feat: allow secret mounts to be specified by env var #121
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
|
Oh nice! Ill have a closer look at this tomorrow. Apologies for the delay here 🙇 |
fishi0x01
approved these changes
Aug 13, 2025
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.
Fixes #120
In order to fix our issue and allow people easy ways to configure mounts instead of relying on auto-discovery, I've added two environment variables that can be used to configure vsh's KV mounts:
VAULT_KV1_MOUNTSandVAULT_KV2_MOUNTS. Comma-delimited strings of paths for each KV version. If non are auto-discovered or configured via these env vars, a default KV2 atsecrets/will be added.