CLI support for exec env configs#1761
Merged
roncodingenthusiast merged 1 commit intoJun 21, 2023
Merged
Conversation
thevilledev
requested review from
roncodingenthusiast
and removed request for
a team
roncodingenthusiast
approved these changes
Jun 20, 2023
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.
Add the following CLI parameters and tests for each one:
exec-env-pristineexec-env-customexec-env-allowlistexec-env-denylistAs
custom,denylistandallowlistare presented in slices, it is possible to define the same parameter multiple times. This behaviour matches how other HashiCorp tools handle similar cases, such as:consul agentand--node-meta<key:value>parametervault kv getand-header=<key=value>Fixes #1051