Repository navigation
chore(secrets): read the jshvn/dispatch-cloudflare vault - #22
Merged
Merged
Conversation
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.
The 1Password references now point at this repository's own vault,
jshvn/dispatch-cloudflare. The repository secretOP_SERVICE_ACCOUNT_TOKENholds the token of a service account that reads that vault and nothing else.The item has already moved and the secret is already set, so
maincan't read its secrets until this merges.Test plan
op://reference on this branch resolves (op run --env-file … -- true, values never printed)op vault listshows onlyjshvn/dispatch-cloudflare