IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2025-02-25 18:45:20 -06:00
Code Issues Packages Projects Releases Wiki Activity

Clarify how the ~> version constraint operator works (#31298)

Browse Source 
* Clarify how the ~> version contraint operator works

* add comma, clarify the actor

* verbiage tweak

* language cleanup from PR review

Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>

* fix line length

Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>
This commit is contained in:
Alan Szlosek Jr 2022-06-27 11:13:14 -04:00 committed by GitHub
parent 126e493818
commit ec4935ba5d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/docs/language/providers/requirements.mdx
View File

@ -247,7 +247,9 @@ A module intended to be used as the root of a configuration — that is, as the
directory where you'd run `terraform apply` — should also specify the
_maximum_ provider version it is intended to work with, to avoid accidental
upgrades to incompatible new versions. The `~>` operator is a convenient
shorthand for allowing only patch releases within a specific minor release:
shorthand for allowing the rightmost component of a version to increment. The
following example uses the operator to allow only patch releases within a
specific minor release:
```hcl
terraform {