This topic provides reference information about the version constraints syntax in Terraform configuration language.
Terraform lets you specify a range of acceptable versions for components you define in the configuration. Terraform expects a specially-formatted string to constrain the versions of the component. You can specify version constraints when configuring the following components:
required_version setting in the terraform block.A version constraint is a string literal containing one or more conditions separated by commas.
Each condition consists of an operator and a version number.
Version numbers are a series of numbers separated by periods, for example 1.2.0. It is optional, but you can include a suffix to indicate a beta release. Refer to Specify a pre-release version for additional information.
Use the following syntax to specify version constraints:
version = "<operator> <version>"
In the following example, Terraform installs a versions 1.2.0 and newer, as well as version older than 2.0.0:
version = ">= 1.2.0, < 2.0.0"
The following table describes the operators you can use to configure version constraints:
Operator Description=,
!= Excludes an exact version number. >,
>=,
<,
<= Compares to a specified version. Terraform allows versions that resolve to true. The > and >= operators request newer versions. The < and <= operators request older versions. ~> Allows only the right-most version component to increment. Examples:
~> 1.0.4: Allows Terraform to install 1.0.5 and 1.0.10 but not 1.1.0.1.1: Allows Terraform to install 1.2 and 1.10 but not 2.0.Terraform uses versions that meet all applicable constraints.
Terraform consults version constraints to determine whether it has acceptable versions of itself, any required provider plugins, and any required modules. For plugins and modules, Terraform uses the newest installed version that meets the applicable constraints.
When Terraform does not have an acceptable version of a required plugin or module, it attempts to download the newest version that meets the applicable constraints.
When Terraform is unable to obtain acceptable versions of external dependencies or if it does not have an acceptable version of itself, then it does not proceed with any terraform plan, terraform apply, or terraform state operations.
The root module and any child modules can constrain the Terraform version and any provider versions the modules use. Terraform considers these constraints equal, and only proceeds if all are met.
Specify a pre-release versionA pre-release version is a version number that contains a suffix introduced by a dash, for example 1.2.0-beta. To configure Terraform to select a pre-release version, set the exact version number using the = operator. You can also omit the operator and specify the exact pre-release version. Terraform does not match pre-release versions on >, >=, <, <=, or ~> operators.
We recommend implementing the following best practices when configuration version constraints.
Module versionsRequire specific versions to ensure that updates only happen when convenient to you when your infrastructure depencds on third-party modules.
Specify version ranges when your organization consistently uses semantic versioning for modules it maintains.
Specify version ranges when your organization follows a well-defined release process that avoids unwanted updates.
Reusable modules should constrain only their minimum allowed versions of Terraform and providers, such as >= 0.12.0. This helps avoid known incompatibilities, while allowing the user of the module flexibility to upgrade to newer versions of Terraform without altering the module.
Root modules should use a ~> constraint to set both a lower and upper bound on versions for each provider they depend on.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4