-
Notifications
You must be signed in to change notification settings - Fork 86
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
fix: added warning for dangling referrers index deletion #619
Conversation
Signed-off-by: Patrick Zheng <[email protected]>
Signed-off-by: Patrick Zheng <[email protected]>
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## main #619 +/- ##
==========================================
- Coverage 34.43% 34.28% -0.15%
==========================================
Files 32 32
Lines 1844 1852 +8
==========================================
Hits 635 635
- Misses 1188 1196 +8
Partials 21 21
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Should the exit code be zero? /cc @toddysm |
@sajayantony I believe so and avoid braking any scripts. Also, is this the only message we will show:
I believe there should still be a confirmation that the operation succeeded and the signature got attached to the artifact. We should show the standard message we show when signature is attached + the warning. |
@@ -22,6 +23,8 @@ const ( | |||
signatureManifestImage = "image" | |||
) | |||
|
|||
const referrersTagSchemaDeleteError = "failed to delete dangling referrers index" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shizhMSFT @Wwwsylvia Since this error is generated based on oras-go-specific procedure, should oras-go export this error so caller can implement upon?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's beyond this PR's scope, I created an issue for tracking, let's move discussion there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah we need to think about how to improve oras-go
for such use case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once oras-go
is updated and have a new release, we can update here. But for now, let's do a string match.
Yes, the exit code should be 0. Once the warning is printed out, |
This warning message is an addition to the standard result. Can refer this in the code. |
Signed-off-by: Patrick Zheng <[email protected]>
Closing this PR due to suggestion here: #615 (comment). |
Reopened based on discussion. |
Signed-off-by: Patrick Zheng <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This PR tries to resolve #615.