-
Notifications
You must be signed in to change notification settings - Fork 11
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
chore: bundle signing #843
base: main
Are you sure you want to change the base?
Conversation
Lingering questions because I know nothing about cosign 😅
|
@@ -38,6 +38,9 @@ const ( | |||
// Bundle pull config keys | |||
V_BNDL_PULL_OUTPUT = "bundle.pull.output" | |||
V_BNDL_PULL_KEY = "bundle.pull.key" | |||
|
|||
// Bundle deploy config keys | |||
V_BNDL_DEPLOY_KEY = "bundle.deploy.key" |
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.
What do you think of bundle.deployKey
? Just thinking of ways to reduce YAML layers
@UncleGedd so what is currently in the PR covers the actual signing of the bundle.yaml similar to what zarf is doing. The difference is that zarf keeps an aggregatechecksum of everything in the zarf.yaml metadata, which we currently don't. We will need to add this to make the signing worth while. That being said, zarf is looking into updating the way that they do signing based on: So not sure where this falls in terms of priority |
Description
Fixes functionality for signing bundles, and verifying, inspecting and deploying signed bundles
Related Issue
Fixes #831
Type of change
Checklist before merging