-
Notifications
You must be signed in to change notification settings - Fork 54
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 cosign initialize as an init container to initialize TUF. #157
Conversation
Codecov Report
@@ Coverage Diff @@
## main #157 +/- ##
=======================================
Coverage 63.40% 63.40%
=======================================
Files 26 26
Lines 2350 2350
=======================================
Hits 1490 1490
Misses 782 782
Partials 78 78 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Hm, so cosign initialize is failing, but looks right to me:
|
Ahaha, the TUF_ROOT env variable is used by sigstore/sigstore TUF to figure out where the root lives. Argh, that means I have to do some mungery until I can fix that in scaffolding. |
Signed-off-by: Ville Aikas <vaikas@chainguard.dev>
Signed-off-by: Ville Aikas <vaikas@chainguard.dev>
Signed-off-by: Ville Aikas <vaikas@chainguard.dev>
Signed-off-by: cpanato <ctadeu@gmail.com>
Signed-off-by: cpanato <ctadeu@gmail.com>
Signed-off-by: Ville Aikas <vaikas@chainguard.dev>
Signed-off-by: Ville Aikas <vaikas@chainguard.dev>
Actually, after looking more deeply at how cosign does it, I do wonder if I should actually use the code from sigstore/sigstore/tuf directly and not bake in the init container. Please hold up on merging. I'll create a different PR to see if it makes more sense. |
Signed-off-by: Ville Aikas vaikas@chainguard.dev
Summary
Release Note
Documentation