Hardening manifest is pushing to wrong path

Summary

This container's hardening manifest has the wrong path. It is telling VAT and Registry1 that it is opensource/goharbor/harbor-core. This is causing it to compete with the real harbor-core for a spot in Registry1. If you visit Registry1, you have a chance of either downloading harbor-core or harbor-log.

Steps to reproduce

View the hardening manifest.

What is the current bug behavior?

This Gitlab project is pushing to harbor-core in the VAT and in registry1, instead of to harbor-log.

What is the expected correct behavior?

This should push to the correct path that matches its project name.

Relevant logs and/or screenshots

Possible fixes

See link in description

Defintion of Done

• Bug has been identified and corrected within the container