feat(hashivault): token helper#2174
Merged
bobcallaway merged 1 commit intosigstore:mainfrom Oct 17, 2025
Merged
Conversation
Signed-off-by: Simon Ostendorf <simon.ostendorf@cancom.de>
cdac2f7 to
c3b6153
Compare
bobcallaway
approved these changes
Oct 17, 2025
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
2 participants
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.
Resolves sigstore/cosign#2861
Summary
I want to use cosign in kubernetes with vault (e.g. with connaisseur).
Currently the token has to be mounted in
~/.vault-tokenor set viaVAULT_TOKEN. When using dynamic regenerated tokens, the vault-agent-injector can/should be used. But the agent injector can only save the token to a file namedtoken.This PR allows token helpers so that a custom token helper can return the vault token that the agent injector injected into the pod.
Release Note
Added ability to use token helpers for Hashicorp Vault.
Documentation
none, the vault-token file is currently not documented either (i guess) and as mentioned in cosign#2861 we are keeping this as near to the vault cli as possible, so its documented there.