-
Notifications
You must be signed in to change notification settings - Fork 176
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: add check during image discovery to make sure images are valid #3234
Conversation
✅ Deploy Preview for zarf-docs canceled.
|
✅ Deploy Preview for zarf-docs canceled.
|
Related to #3253 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
|
Signed-off-by: Allen Conlon <[email protected]>
06ee1fd
to
b2b355c
Compare
Any reason those two test are stuck? |
GitHub reports "unexpected error" - so I'm going to give those a retry real quick. |
Ah, thank you very much!! |
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.
This definitely improves the baseline. I'll let another maintainer weigh-in if there is any patterns or constraints we want to follow with regards to the regex logic - otherwise LGTM.
Thanks!! I was a little worried that because you all are migrating to |
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. Good test case and defense for the logic. Matching the license and incl. attribution makes accepting this easy. Nice job
I would be happy to help with the effort to port over to the |
Thanks Team!! |
Description
When using
zarf
to discover images with the Ironbank chartkyverno-policies
, therestrict-image-registries
policy, (simple version included in tests), has an entry of:registry.dso.mil/*
This is a false positive and cases cosign looks up to fail as that is not a valid image.
Checklist before merging