Skip to content
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

Handle 404s from harbor #304

Merged
merged 1 commit into from
May 28, 2020
Merged

Conversation

ekcasey
Copy link
Member

@ekcasey ekcasey commented May 28, 2020

Harbor doesn't seem to return the error code specified in the registry api docs when a manifest is not found. This PR bumps imgutil to a version that gracefully handles all 404s without regard for the specific error code

Resolves #303

Harbor doesn't seem to return the error code specified in the registry api docs when a manifest is not found. This PR bumps imgutil to a version that gracefully handles all 404s without regarding for the specific error code

Signed-off-by: Emily Casey <[email protected]>
@ekcasey ekcasey requested a review from a team as a code owner May 28, 2020 21:20
@ekcasey ekcasey requested a review from matthewmcnew May 28, 2020 21:20
@ekcasey ekcasey added this to the lifecycle-0.7.6 milestone May 28, 2020
@matthewmcnew
Copy link
Contributor

❤️ Thanks!

@ekcasey ekcasey merged commit 7a3b172 into master May 28, 2020
@ekcasey ekcasey deleted the bugfix/303-harbor-manifest-not-found branch May 28, 2020 22:42
@ekcasey ekcasey modified the milestones: lifecycle-0.7.6, lifecycle-0.8.0 May 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Analyze fails checking nonexistent manifest on harbor 2
2 participants