feat: added double asterisk wildcard selector to prevent uppercasing of keys before exporting envs#545
Merged
fairclothjm merged 3 commits intohashicorp:mainfrom Mar 3, 2025
Merged
Conversation
…of keys before exporting envs
|
|
|
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Have you signed the CLA already but the status is still pending? Recheck it. |
Contributor
Author
|
fyi i've signed the CLA but it wont change status for some reason |
1 task
It might be if you submitted a change under your email, instead of your GitHub handle for example. That's fairly common. |
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
3 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.
Description
When using the wildcard to match multiple secrets to export as env variables, all keys get uppercased. There are situations where this is undesirable. To maintain backwards compatibility I've added an alterative double asterisk
**which will avoid uppercasing exported env keys.Relates #537
Closes #536
Checklist
Community Note
reaction
to the original pull request comment to help the community and maintainers
prioritize this request
followers and do not help prioritize the request