You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
thanks for opening this - just in case it is not clear, it would be ideal if nomad plan read VAULT_TOKEN from the environment if vault-token is not specified, the same as other commands
This PR fixes a regression where the 'job plan' command would not respect
a Vault token if set via --vault-token or $VAULT_TOKEN.
Basically the same bug/fix as for the validate command in #13062Fixes#13939
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
This PR fixes a regression where the 'job plan' command would not respect
a Vault token if set via --vault-token or $VAULT_TOKEN.
Basically the same bug/fix as for the validate command in hashicorp#13062Fixeshashicorp#13939
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
#13062 (comment)
The text was updated successfully, but these errors were encountered: