-
Notifications
You must be signed in to change notification settings - Fork 395
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
allow to pass a list of docker images to attest #454
Comments
PS: if this is something you're interested in, I'm happy to try and contribute it, and/or test it :) |
@caarlos0 this is definitely something we're looking at. There have been multiple requests to support attestation of multiple images at once. There is some internal plumbing that needs to be tackled in order to make this work properly with the I recently added support for identifying subjects with a checksums file (which was actually done in response to a request for better GoReleaser integration). If you are NOT using the
|
Hmmm interesting, I'll experiment with that as well! I saw the checksums option, it's awesome! Thanks for that 🙏 |
|
Fixes actions#454 Add support for passing a list of docker images to attest. * **action.yml** - Add a new input parameter `subject-images` to accept a list of docker images. - Update the `runs` section to handle the `subject-images` input. * **src/main.ts** - Import `parseMultiImageInput` function from `utils.ts`. - Add logic to handle the `subject-images` input and process multiple docker images for attestation. * **README.md** - Update the documentation to include usage instructions for the `subject-images` input. - Add an example for attesting multiple docker images. * **__tests__/main.test.ts** - Add test cases to verify the functionality of attesting multiple docker images using the `subject-images` input. * **src/utils.ts** - Add a new file to include the `parseMultiImageInput` function to parse the `subject-images` input. --- For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/actions/attest-build-provenance/issues/454?shareId=XXXX-XXXX-XXXX-XXXX).
Hey!
So, I was thinking it would make things a lot easier if we could do this:
The list could then be built on-the-fly if you're using, for example, GoReleaser:
I think this would make an awesome addition, and would make attestation as lot easier as well.
For disclosure: I'm the author of GoReleaser.
The text was updated successfully, but these errors were encountered: