feat(vault-token): add optional vault enterprise namespace variable #108
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.
Added an optional envvar to vault-token module to handle communicating with a non default vault namespace.
in vault enterprise, you can run multiple secure isolated vault environments from the one vault server.
each namespace has it's own authentication methods and secrets engines.
vault uses the VAULT_NAMESPACE envvar to determine the namespace to use.
no value, or either
root
or/
will use the root (default) namespace, any other value will use a different namespacein vault community edition, the only supported namespace is "root", no other namespaces can be used.
in HCP vault dedicated (the saas hosted version), you cant access vault without a namespace set
this defaults to not setting the env var, so is backwards compatible, and works with vault CE