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
As the current Consul implementation is done, if using tokens, it's required to define them in each consul_keys resources. It makes a lot of sense as it provides flexibility. But it's currently not possible to define a default token to be used in the provider definition though.
In my current use case, we only have one token. It would be great if we could define it in the provider and don't have to define it in every consul_keys we have.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 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.
ghost
locked and limited conversation to collaborators
Apr 11, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As the current Consul implementation is done, if using tokens, it's required to define them in each consul_keys resources. It makes a lot of sense as it provides flexibility. But it's currently not possible to define a default token to be used in the provider definition though.
In my current use case, we only have one token. It would be great if we could define it in the provider and don't have to define it in every consul_keys we have.
The text was updated successfully, but these errors were encountered: