ff4ea042c2
The existing "type" argument allows specifying a type constraint that
allows for some basic validation, but often there are more constraints on
a variable value than just its type.
This new feature (requiring an experiment opt-in for now, while we refine
it) allows specifying arbitrary validation rules for any variable which
can then cause custom error messages to be returned when a caller provides
an inappropriate value.
variable "example" {
validation {
condition = var.example != "nope"
error_message = "Example value must not be \"nope\"."
}
}
The core parts of this are designed to do as little new work as possible
when no validations are specified, and thus the main new checking codepath
here can therefore only run when the experiment is enabled in order to
permit having validations.
|
||
|---|---|---|
| .. | ||
| depends_on.tf | ||
| destroy-provisioners.tf | ||
| ignore_changes.tf | ||
| provider_ref.tf | ||
| provisioner_keyword.tf | ||
| redundant_interp.tf | ||
| variable_type_quoted.tf | ||
| variable_validation_experiment.tf | ||