-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Provider blocks unaware of externally given variables #124
Comments
The provider should be seeing this. Are these both your complete files? I don't see a declaration of Can you paste all of your exact files (properly censored)? |
Oops! I was definitely missing the previous variable declaration. Also I did a little more digging and I think the provider block is seeing things just fine, and I have just duplicated this issue. Provider blocks seem to be working fine, no distinction from any other block. FWIW, Here it is as I have it now:
With things like this,
When I run
Sorry for the misdirection! |
Updates the docs and clarifies the usage of `do_token` variable. I was experiencing an issue mentioned here #124 and so adding more docs should be helpful.
Updates the docs and clarifies the usage of `do_token` variable. I was experiencing an issue mentioned here hashicorp#124 and so adding more docs should be helpful.
Updates the docs and clarifies the usage of `do_token` variable. I was experiencing an issue mentioned here hashicorp/terraform#124 and so adding more docs should be helpful.
When given the two files:
We get this error:
${var.size}
seems to work fine.Changing the configuration to this:
Seems to remove the error.
Similarly, just passing things in over the command line with
-var
or specifically invoking the-var-file
argument produces the same behavior outlined above, where directly referencing the given arguments results in an error, but adding an indirect variable block fixes it.It seems like the provider block is not accessing externally given variables. I'm able to produce this with the
aws
provider as well.The text was updated successfully, but these errors were encountered: