This website requires JavaScript.
Explore
Help
Sign In
resilien
/
terraform
Watch
2
Star
0
Fork
You've already forked terraform
0
Code
Issues
Pull Requests
Projects
Releases
Wiki
Activity
0d614a8d01
terraform
/
config
/
testdata
/
variable-no-name.tf
9 lines
99 B
Terraform
Raw
Normal View
History
Unescape
Escape
config: generate errors for unnamed blocks of various sources We've been incorrectly validating (or not validating at all) the requirement that certain blocks be followed by a name string, to prohibit e.g. this: variable {} and: variable = "" Before this change we were catching this for most constructs only if there were no _valid_ blocks of the same name in the same file. For modules in particular, we were not catching this at all. Now we detect this for all kinds of block (resources had a pre-existing check, so aren't touched here) and produce a different error message depending on which of the above incorrect forms are used. This fixes #13575.
2017-05-03 00:42:34 +02:00
variable
"
okay
"
{
}
config: manually parse variable blocks for better validation Fixes #7846 This changes from using the HCL decoder to manually decoding the `variable` blocks within the configuration. This gives us a lot more power to catch validation errors. This PR retains the same tests and fixes one additional issue (covered by a test) in the case where a variable has no named assigned.
2016-11-02 22:59:16 +01:00
variable
{
name
=
"
test
"
default
=
"
test_value
"
type
=
"
string
"
}