Mixing variable definition and specification is order specific

[darrensony]

From: https://www.terraform.io/docs/configuration/load.html

The order of variables, resources, etc. defined within the configuration doesn't matter. Terraform configurations are declarative, so references to other resources and variables do not depend on the order they're defined.

However, it appears that a empty (forward) declaration that occurs after a value declaration unsets the value.

To wit, this works:

variable "test" {}
variable "test" { default = "5" }

But swap the order, and it queries for a value for "test":

variable "test" { default = "5" }
variable "test" {}

Expected Behaviour: A late forward declaration should be silently ignored if there is already a value set for that variable in the symbol table.

[mitchellh]

The real validation here is that a variable should only be allowed to be defined once. Fixed in referenced PR.

[ghost]

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.