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

fix: harbor error support #2619

Merged
merged 2 commits into from
Oct 25, 2021

Conversation

mattpolzin
Copy link
Contributor

What this PR does / why we need it:

This PR addresses the issue I indirectly reported in this comment: #2418 (comment).

I am happy to open a new issue if that is desirable.

In short, the missing image error message given by Harbor used to happen to match the existing hard-coded check Garden performs. After updating the version of Harbor used for our internal image registry, my org started to see Garden fail to build images instead of recognizing that the image had just not been built at the current tag before.

Which issue(s) this PR fixes:

N/A

Special notes for your reviewer:

N/A

@ghost
Copy link

ghost commented Oct 14, 2021

Changes to your CodeSee Architecture Map:

View a CodeSee Map of these changes

View this PR diagram as an interactive map

View more CodeSee Maps

Legend

CodeSee Map Legend

@mattpolzin mattpolzin changed the title Feature/harbor error support fix: harbor error support Oct 14, 2021
@eysi09
Copy link
Collaborator

eysi09 commented Oct 23, 2021

Hi @mattpolzin!

Thank you so much for the submitting a fix for this, and our apologies for the late reply. We've been on the road, travelling for KubeCon among other things so a bit behind schedule.

The fix looks good to me. Any thoughts @edvald?

@edvald edvald merged commit edd5e3f into garden-io:master Oct 25, 2021
@mattpolzin mattpolzin deleted the feature/harbor-error-support branch October 25, 2021 15:12
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.

3 participants