-
Notifications
You must be signed in to change notification settings - Fork 24
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
Expand parameters for container image building #426
Conversation
bc19ebe
to
28f63b4
Compare
This adds the following: * Expanded container metadata for the built image. * multi-architecture builds * Docker SBOM generation * Provenance information generation The intention is to keep a similar set of tags generated as before. Signed-off-by: Juan Antonio Osorio <[email protected]>
28f63b4
to
ac69dbc
Compare
Signed-off-by: Juan Antonio Osorio <[email protected]>
4a958e0
to
ba72609
Compare
Signed-off-by: Juan Antonio Osorio <[email protected]>
f3791d4
to
ac931e4
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.
A NB LGTM @JAORMX , but needs an approved commiter
@calebbrown are you able to review?
tags: ${{ steps.docker-metadata.outputs.tags }} | ||
labels: ${{ steps.docker-metadata.outputs.labels }} |
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.
How does the output of this differ when compared the previous implementation for the value of $VERSION
?
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.
should be quite similar as it uses the tag as well, and it strips the v
prefix just using github action options. This adds even more metadata to the image.
This adds the following:
The intention is to keep a similar set of tags generated as before.
this also separates the pre-existing docker workflow into two jobs:
This ensures that we get test coverage for image builds while keeping the GitHub actions permissions minimal.