We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I can not use this action to sign a container with sigstore when pushing it.
Add an option to the GitHub Action to be able to pass a sigstore private key to use when pushing to sign the containers.
The cosign action does not let me push and sign a container in a single atomic step.
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/building_running_and_managing_containers/assembly_signing-container-images_building-running-and-managing-containers#proc_signing-container-images-with-sigstore-signatures-using-a-private-key_assembly_signing-container-images
The text was updated successfully, but these errors were encountered:
CC @vrothberg
Sorry, something went wrong.
Add support for signing with Sigstore
e59e7ad
Fixes: redhat-actions#89
b529625
bb17792
91ae4bc
Successfully merging a pull request may close this issue.
Is your feature request related to a problem? Please describe.
I can not use this action to sign a container with sigstore when pushing it.
Describe the solution you'd like
Add an option to the GitHub Action to be able to pass a sigstore private key to use when pushing to sign the containers.
Describe alternatives you've considered
The cosign action does not let me push and sign a container in a single atomic step.
Additional context
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/building_running_and_managing_containers/assembly_signing-container-images_building-running-and-managing-containers#proc_signing-container-images-with-sigstore-signatures-using-a-private-key_assembly_signing-container-images
The text was updated successfully, but these errors were encountered: