-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SBOM
accessory that is replicated over from another registry is not deleted after triggering SBOM manual generation
#20496
Labels
Comments
According to our discussion in design stage, Ui will Use the first item in the accessories list. i think the order of item in the list returned fro the backend does not correct. we should always put the latest one in the first item of the list. |
wy65701436
added a commit
to wy65701436/harbor
that referenced
this issue
May 28, 2024
fixes goharbor#20496 Harbor will reserve one SBOM accessory artifact for each subject artifact. Ensure all existing SBOMs are removed before generating the next set. Signed-off-by: wang yan <wangyan@vmware.com>
wy65701436
added a commit
to wy65701436/harbor
that referenced
this issue
May 28, 2024
fixes goharbor#20496 Harbor will reserve one SBOM accessory artifact for each subject artifact. Ensure all existing SBOMs are removed before generating the next set. Signed-off-by: wang yan <wangyan@vmware.com>
wy65701436
added a commit
to wy65701436/harbor
that referenced
this issue
May 28, 2024
fixes goharbor#20496 Harbor will reserve one SBOM accessory artifact for each subject artifact. Ensure all existing SBOMs are removed before generating the next set. Signed-off-by: wang yan <wangyan@vmware.com>
wy65701436
added a commit
to wy65701436/harbor
that referenced
this issue
May 29, 2024
fixes goharbor#20496 Harbor will reserve one SBOM accessory artifact for each subject artifact. Ensure all existing SBOMs are removed before generating the next set. Signed-off-by: wang yan <wangyan@vmware.com>
wy65701436
added a commit
to wy65701436/harbor
that referenced
this issue
May 29, 2024
fixes goharbor#20496 Harbor will reserve one SBOM accessory artifact for each subject artifact. Ensure all existing SBOMs are removed before generating the next set. Signed-off-by: wang yan <wangyan@vmware.com> Signed-off-by: wang yan <wangyan@vmware.com>
wy65701436
added a commit
to wy65701436/harbor
that referenced
this issue
May 29, 2024
fixes goharbor#20496 Harbor will reserve one SBOM accessory artifact for each subject artifact. Ensure all existing SBOMs are removed before generating the next set. Signed-off-by: wang yan <wangyan@vmware.com> Signed-off-by: wang yan <wangyan@vmware.com>
wy65701436
added a commit
that referenced
this issue
May 29, 2024
fix 20496 fixes #20496 Harbor will reserve one SBOM accessory artifact for each subject artifact. Ensure all existing SBOMs are removed before generating the next set. Signed-off-by: wang yan <wangyan@vmware.com>
wy65701436
added a commit
to wy65701436/harbor
that referenced
this issue
May 29, 2024
fix 20496 fixes goharbor#20496 Harbor will reserve one SBOM accessory artifact for each subject artifact. Ensure all existing SBOMs are removed before generating the next set. Signed-off-by: wang yan <wangyan@vmware.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How to reproduce?
The text was updated successfully, but these errors were encountered: