terraform/internal/command/testdata/init-check-required-version/main.tf

terraform {
    required_version = "~> 0.9.0"
}

terraform {
    required_version = ">= 0.13.0"
}
command/init: check required_version Previously we were checking required_version only during "real" operations, and not during initialization. Catching it during init is better because that's the first command users run on a new working directory. 2017-08-28 20:25:16 +02:00			`terraform {`
			`required_version = "~> 0.9.0"`
			`}`
terraform: Fix required version constraint diags If a module has multiple terraform.required_version constraints, any failures would point at the last constraint in the error diagnostics. If an earlier constraint was the actual problem, this leads to confusing errors like this: Error: Unsupported Terraform Core version on main.tf line 6, in terraform: 6: required_version = ">= 0.13.0" This configuration does not support Terraform version 0.13.0. The error was due to storing the declaration range of the constraint as a pointer to the contents of a loop variable, which was later overwritten in later iterations of the loop. Instead we now use HCL's handy Ptr() method to create a direct pointer to the range struct. 2020-08-18 15:18:00 +02:00
			`terraform {`
			`required_version = ">= 0.13.0"`
			`}`