From ec4935ba5db516ebe24bf2d26a31fcd2db518b5d Mon Sep 17 00:00:00 2001 From: Alan Szlosek Jr Date: Mon, 27 Jun 2022 11:13:14 -0400 Subject: [PATCH] Clarify how the ~> version constraint operator works (#31298) * 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> --- website/docs/language/providers/requirements.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/docs/language/providers/requirements.mdx b/website/docs/language/providers/requirements.mdx index 8331bd74e2..f83d930399 100644 --- a/website/docs/language/providers/requirements.mdx +++ b/website/docs/language/providers/requirements.mdx @@ -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 {