You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+19-6Lines changed: 19 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,8 +91,15 @@ to perform a deep map merge of standard Terraform maps and objects.
91
91
## Usage
92
92
93
93
94
-
**IMPORTANT:** The `master` branch is used in `source` just as an example. In your code, do not pin to `master` because there may be breaking changes between releases.
95
-
Instead pin to the release tag (e.g. `?ref=tags/x.y.z`) of one of our [latest releases](https://github.com/cloudposse/terraform-yaml-config/releases).
94
+
**IMPORTANT:** We do not pin modules to versions in our examples because of the
95
+
difficulty of keeping the versions in the documentation in sync with the latest released versions.
96
+
We highly recommend that in your code you pin the version to the exact version you are
97
+
using so that your infrastructure remains stable, and update versions in a
98
+
systematic way so that they do not catch you by surprise.
99
+
100
+
Also, because of a bug in the Terraform registry ([hashicorp/terraform#21417](https://github.com/hashicorp/terraform/issues/21417)),
101
+
the registry shows many of our inputs as required when in fact they are optional.
102
+
The table below correctly indicates which inputs are required.
96
103
97
104
98
105
For a complete example, see [examples/complete](examples/complete).
@@ -114,7 +121,9 @@ For an example of using remote config maps with `import` and deep merging into a
0 commit comments