-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
consul_keys data source ignores provider datacenter #8
Labels
Comments
As result of investigation - roots of this issue the same as in #13 |
Maybe we can close #13 in favor of this one. |
remilapeyre
added a commit
to remilapeyre/terraform-provider-consul
that referenced
this issue
May 12, 2021
…ovider configuration This also adds test with multiple datacenter, we were not testing this configuration until now. The tests are not run by default to not make local development more complicated but are run in CI both with Consul Community Edition and Consul Enterprise. Closes hashicorp#8
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue was originally opened by @hexedpackets as hashicorp/terraform#9310. It was migrated here as part of the provider split. The original body of the issue is below.
Terraform Version
0.7.5
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
The datacenter specified in the provider is used to retrieve the key.
Actual Behavior
The agent's default datacenter is used instead of the one specified in the provider, resulting in an empty or incorrect value.
Adding the datacenter argument to the consul_keys stanza as a workaround does cause the correct datacenter to be used.
The text was updated successfully, but these errors were encountered: