mirror of
https://github.com/hashicorp/terraform.git
synced 2026-03-21 18:10:30 -04:00
3b620bfe69
Previously we introduced a language experiment that would permit variable validation rules to refer to other objects declared in the same module as the variable. Now that experiment is concluded and its behavior is available for all modules. This final version deviates slightly from the experiment: we learned from the experimental implementation that we accidentally made the "validate" command able to validate constant-valued input variables in child modules despite the usual rule that input variables are unknown during validation, because the previous compromise bypassed the main expression evaluator and built its own evaluation context directly. Even though that behavior was not intended, it's a useful behavior that is protected by our compatibility promises and so this commit includes a slightly hacky emulation of that behavior, in eval_variable.go, that fetches the variable value in the same way the old implementation would have and then modifies the hcl evaluation context to include that value, while preserving anything else that our standard evaluation context builder put in there. That narrowly preserves the old behavior for expressions that compare the variable value directly to a constant, while treating all other references (which were previously totally invalid) in the standard way. This quirk was already covered by the existing test TestContext2Validate_variableCustomValidationsFail, which fails if the special workaround is removed.
18 lines
321 B
HCL
18 lines
321 B
HCL
|
|
locals {
|
|
foo = 1
|
|
}
|
|
|
|
variable "validation" {
|
|
validation {
|
|
condition = local.foo == var.validation
|
|
error_message = "Must be five."
|
|
}
|
|
}
|
|
|
|
variable "validation_error_expression" {
|
|
validation {
|
|
condition = var.validation_error_expression != 1
|
|
error_message = "Cannot equal ${local.foo}."
|
|
}
|
|
}
|