Repository navigation
Support default services for trusted-root and signing-config creation - #4592
Merged
Merged
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #4592 +/- ##
==========================================
- Coverage 40.10% 36.05% -4.05%
==========================================
Files 155 220 +65
Lines 10044 12413 +2369
==========================================
+ Hits 4028 4476 +448
- Misses 5530 7241 +1711
- Partials 486 696 +210 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Hayden-IO
force-pushed
the
default-services
branch
4 times, most recently
from
December 22, 2025 04:54
65a7104 to
c4d942b
Compare
When a client doesn't want to use a default service like Rekor while still using the public instance, a client would need to retrieve the signing configuration or trusted root, remove the tlog sections, and provide that to the sign/verify command. This first step can now be skipped by using --with-default-services and --no-<service> to omit it from the configuration file. This will provide a better user experience while maintaining the unified configuration interface between clients. Ref: docker/actions-toolkit#901 Signed-off-by: Hayden <8418760+haydentherapper@users.noreply.github.com>
Hayden-IO
force-pushed
the
default-services
branch
from
December 22, 2025 05:11
c4d942b to
0035278
Compare
Contributor
Author
|
Verified working with |
fghanmi
pushed a commit
to securesign/cosign
that referenced
this pull request
Jan 22, 2026
…sigstore#4592) When a client doesn't want to use a default service like Rekor while still using the public instance, a client would need to retrieve the signing configuration or trusted root, remove the tlog sections, and provide that to the sign/verify command. This first step can now be skipped by using --with-default-services and --no-<service> to omit it from the configuration file. This will provide a better user experience while maintaining the unified configuration interface between clients. Ref: docker/actions-toolkit#901 Signed-off-by: Hayden <8418760+haydentherapper@users.noreply.github.com>
7 tasks
This file contains hidden or 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
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.
When a client doesn't want to use a default service like Rekor while still using the public instance, a client would need to retrieve the signing configuration or trusted root, remove the tlog sections, and provide that to the sign/verify command. This first step can now be skipped by using
--with-default-servicesand--no-<service>to omit it from the configuration file. This will provide a better user experience while maintaining the unified configuration interface between clients.Ref: docker/actions-toolkit#901
Summary
Release Note
Documentation