Skip to content
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

Add flags for bringing in existing private key. fix secret names to b… #363

Merged
merged 2 commits into from
Oct 18, 2022

Conversation

vaikas
Copy link
Contributor

@vaikas vaikas commented Oct 18, 2022

…e consistent.

Signed-off-by: Ville Aikas vaikas@chainguard.dev

Description of the change

Add flags for bringing in an existing secret.

Existing or Associated Issue(s)

Additional Information

Checklist

  • Chart version bumped in Chart.yaml according to semver. Where applicable, update and bump the versions in any associated umbrella chart
  • Variables are documented in the values.yaml and added to the README.md. The helm-docs utility can be used to generate the necessary content. Use helm-docs --dry-run to preview the content.
  • JSON Schema generated.
  • List tests pass for Chart using the Chart Testing tool and the ct lint command.

…e consistent.

Signed-off-by: Ville Aikas <vaikas@chainguard.dev>
@@ -92,6 +92,10 @@ createctconfig:
logPrefix: sigstorescaffolding
privateKeyPasswordSecretName: ""
ttlSecondsAfterFinished: 3600
pubkeysecret: "ctlog-public-key"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these just defaults? Does this value exist in prod?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, these are just the defaults 👍

Signed-off-by: Ville Aikas <vaikas@chainguard.dev>
@vaikas vaikas merged commit 3df696e into sigstore:main Oct 18, 2022
@vaikas vaikas deleted the existing-secret-in-ctlog branch October 18, 2022 23:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants