Repository navigation
Add OIDC-authenticated key-value store actions - #30
Merged
Merged
Conversation
This was referenced Oct 22, 2026
zaniebot
force-pushed
the
zb/oidc-key-value-actions
branch
from
October 22, 2026 04:18
6e01e0c to
a45012f
Compare
zanieb
marked this pull request as ready for review
October 22, 2026 04:22
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.
Add
key-value-store/get,key-value-store/put, andkey-value-store/deleteto share small values within a GitHub Actions OIDC context. Each invocation exchanges a fresh OIDC token for a short-lived session. The service assigns separate namespaces to different pull requests; workflows for the same pull request and environment can share keys.All three actions take
service-url,key, and an optionalaudience, and requireid-token: write.putaccepts UTF-8 text throughvalueor raw bytes throughpath, up to 64 KiB.getreturnsfound,value,path, andexpires-at; a missing key succeeds withfound: 'false', while an empty value hasfound: 'true'. Whengetwrites topath, the file must not already exist. Deleting an absent key succeeds.Namespace isolation is enforced by the service. All actors and jobs within one accepted OIDC context share read, write, and delete access, and anyone holding a session token can use it until expiry. OIDC and session tokens are not action outputs, redirects are rejected, and retrieved text is masked by default. The service endpoint, audience, and file paths must be trusted, including the parent directories of file paths; retrieved values remain untrusted data.
The README includes usage examples and documents the action inputs, outputs, and service API.