Add documentation on generating trusted_root.json #1174
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The TUF mirror in this scaffolding stack does not serve a trusted_root.json, which is needed by sigstore-go to verify artifacts signed using a private sigstore deployment. Add documentation so that users can create this themselves using available community tooling. This may eventually be turned into part of the GitHub action so that clients can use the action for integration testing. Signed-off-by: Colleen Murphy <colleenmurphy@google.com>
jku
approved these changes
Jul 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The TUF mirror in this scaffolding stack does not serve a trusted_root.json, which is needed by sigstore-go to verify artifacts signed using a private sigstore deployment. Add documentation so that users can create this themselves using available community tooling. This may eventually be turned into part of the GitHub action so that clients can use the action for integration testing.
I couldn't find an official way of generating this file that felt safe to include as part of the createsecret service, but I still wanted to write this down so others don't fall down the same rabbit hole wondering why a client needs this apparently missing file. I used this to generate the trusted material for this PR because I needed to test the changes with a custom OIDC provider.
Summary
Release Note
Documentation