Request Bitwarden Secrets Manager secrets as JSON#1570
Merged
djmb merged 1 commit intobasecamp:mainfrom Jun 16, 2025
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
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.
Currently the Bitwarden Secrets Manager adapter requests secrets using the
-o envoutput option, and then splits the results on/nto build an array of secrets. This breaks if the secret key value includes the string"/n"(in my case, it was a SSH key value).This PR updates the secrets commands to use the default Bitwarden Secrets Manager CLI JSON output format, which should not be affected by any weird key values.