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.
Adds seekrit at the bottom of Secret Management.
What distinguishes it from the neighbours already in that section: the server stores only ciphertext. Keys are generated and held client-side, so encryption and decryption happen in the CLI, in an egress proxy, or in a read-path SDK — never in the API.
Delivery paths a DevOps reader would care about:
seekrit run -- <cmd>injects decrypted secrets into a child process's environment (no.envon disk){{seekrit:NAME}}placeholders in outbound requests behind a default-deny allowlist, so a workload can call an API without holding the keyDisclosure: I maintain seekrit. Happy to shorten the description if it runs long for the section's style.