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
There is a vault_namespace data source for getting the current namespace, but there does not appear to be any way of getting the current server address. We're having to pass that around using variables, which is error-prone. It would be nice if there was either another data source that exposed the address parameter of the provider config, or if vault_namespace was extended to also report the address.
Affected Resource(s) and/or Data Source(s)
No response
Potential Terraform Configuration
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered:
Description
There is a
vault_namespace
data source for getting the current namespace, but there does not appear to be any way of getting the current server address. We're having to pass that around using variables, which is error-prone. It would be nice if there was either another data source that exposed theaddress
parameter of the provider config, or ifvault_namespace
was extended to also report the address.Affected Resource(s) and/or Data Source(s)
No response
Potential Terraform Configuration
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: