-
Notifications
You must be signed in to change notification settings - Fork 55
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
bib/internal/setup: Tag validate early #475
Conversation
Working, testing by hand
|
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.
Thank you (and sorry for the somewhat slow reply, we are usually quicker with reviews)!
This looks very nice - I have some suggestions inline about the testing, it includes two potential git commits that could be used here to. Once the testing is sorted this looks good to go to me (but an additonal pair of eyes on this from e.g. @achilleas-k would be nice)
@mvo5 I incorporated your patches. My editor applied my default formatting, not sure there is a formatter the project uses. I had an issue with
The specific tag tests were passing though.
|
Thank you for the updated PR!
The formatitng changes are something we would like to avoid. The diff should just contain the functional changes. It might be easiest to just "git am" the two patches from #475 (comment) and force push. Note that the "happy" path of ValidateHasContainerTags is tested implicitly by any of the "test_{build,manifest}.py" that test a valid image (e.g. test_manifest..yy::test_manifest_smoke).
[..] Thank you! I will try to reproduce, is there anything unusual about your setup that might help me to reproduce? |
f174336
to
74eab7b
Compare
I got a bit lost reviewing that last commit with all the formatting changes so I edited the commits a bit. Broke out the octal literal format change into its own commit, reverted the formatting changes 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.
Thanks for the contribution. This LGTM!
74eab7b
to
28a4603
Compare
Check that the container has the expected bootc tags early and fail if they are missing.
Use `0o` instead of just `0` for better readability.
Create a mock podman executable script and add it at the top of PATH. Use it to generate output for the container tag validation.
28a4603
to
c044c78
Compare
Rebased and resolved conflict. |
Add new `test_manifest_checks_build_container_is_bootc` test that validates that `botoc-iamge-build manifest` fails with the expected error on a non-bootc image url. Note that this will implicitly check `build` too as the same check is performed in bib for manifest and build (i.e. bib needs to generate a manifest first before it can build). Co-authored-by: bstrausser <bstrausser@locusrobotics.com>
c044c78
to
3dc4b1e
Compare
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.
Thank you!
This is my first attempted commit to this project.
I'm still learning the repo structure and dev workflow. Few questions on testing.
Closes: #380