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: _docs-sources/iac/stay-up-to-date/updating.md
+97Lines changed: 97 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,6 @@
1
+
import Tabs from '@theme/Tabs';
2
+
import TabItem from '@theme/TabItem';
3
+
1
4
# Updating
2
5
3
6
Updating a module or service requires changing the tagged version in the `source` attribute of the module block. For backwards compatible changes, this is as simple as incrementing the version number. For backwards incompatible changes, refer to the release notes for a migration guide in each module's Github repository release page.
@@ -6,6 +9,9 @@ We recommend updating module versions in your development environment first, fol
Below is a module block referencing version `0.15.3` of the `single-server` submodule from the `terraform-aws-server` module.
10
16
11
17
To update to version `0.15.4`, you update the value to the right of `ref=` in the source attribute. Since the version number denotes that this update is backwards compatible, it should not require any other changes.
@@ -29,6 +35,97 @@ module "my_instance" {
29
35
```
30
36
31
37
After making the change, run `terraform plan`, inspect the output to ensure it looks as you expect, then run `terraform apply`.
38
+
</TabItem>
39
+
<TabItemvalue="Terragrunt"label="Terragrunt">
40
+
41
+
Below is a module block referencing version `0.15.3` of the `single-server` submodule from the `terraform-aws-server` module.
42
+
43
+
To update to version `0.15.4`, you update the value to the right of `ref=` in the source attribute. Since the version number denotes that this update is backwards compatible, it should not require any other changes.
After making the change, run `terragrunt plan`, inspect the output to ensure it looks as you expect, then run `terragrunt apply`.
75
+
76
+
</TabItem>
77
+
<TabItemvalue="Terragrunt with _envcommon"label="_envcommon (Terragrunt)">
78
+
79
+
When following the `_envcommon` pattern, there are two places that reference the git tag created by the release — the `.hcl` file with the reference to the module in the `_envcommon` directory and the environment and region specific references to the _envcommon file.
80
+
81
+
Below is an example using the `_envcommon` pattern to reference version `0.15.3` of the `single-server` submodule from the `terraform-aws-server` module. To update to version `0.15.4`, you update the value to the right of `ref=` in the source attribute. Since the version number denotes that this update is backwards compatible, it should not require any other changes.
Copy file name to clipboardExpand all lines: _docs-sources/iac/stay-up-to-date/versioning.md
+88Lines changed: 88 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,6 @@
1
+
import Tabs from '@theme/Tabs';
2
+
import TabItem from '@theme/TabItem';
3
+
1
4
# Versioning
2
5
3
6
Gruntwork versions the IaC library using [Semantic Versioning](https://semver.org/) (SemVer). Since much of the Gruntwork IaC Library is still pre-1.0.0, most of the Gruntwork IaC Library uses 0.MINOR.PATCH version numbers. With 0.MINOR.PATCH, the rules are a bit different, where we increment the:
@@ -13,6 +16,9 @@ We release new module versions using GitHub releases, refer to the release notes
<TabItemvalue="Terragrunt with _envcommon"label="_envcommon (Terragrunt)">
75
+
76
+
When following the `_envcommon` pattern, there are two places that reference the git tag created by the release.
77
+
78
+
First, locate the file in which you are referencing the module in your `_envcommon` directory. Then, reference the git tag in the `source` argument for the `terraform` block in the file.
79
+
80
+
For example, if you were referencing the `single-server` module, your file path might look like the following:
Then, reference the git tag in the `source` argument for the `terraform` block in the `terragrunt.hcl` environment and region specific files that reference the file in the `_envcommon` directory. For example, if you were using this module to create a single EC2 instance in your development environment in the us-west-2 region of AWS, your file path would be `/dev/us-west-2/services/single_ec2_instance/terragrunt.hcl`.
Copy file name to clipboardExpand all lines: docs/iac/stay-up-to-date/updating.md
+98-1Lines changed: 98 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,6 @@
1
+
import Tabs from '@theme/Tabs';
2
+
import TabItem from '@theme/TabItem';
3
+
1
4
# Updating
2
5
3
6
Updating a module or service requires changing the tagged version in the `source` attribute of the module block. For backwards compatible changes, this is as simple as incrementing the version number. For backwards incompatible changes, refer to the release notes for a migration guide in each module's Github repository release page.
@@ -6,6 +9,9 @@ We recommend updating module versions in your development environment first, fol
Below is a module block referencing version `0.15.3` of the `single-server` submodule from the `terraform-aws-server` module.
10
16
11
17
To update to version `0.15.4`, you update the value to the right of `ref=` in the source attribute. Since the version number denotes that this update is backwards compatible, it should not require any other changes.
@@ -29,6 +35,97 @@ module "my_instance" {
29
35
```
30
36
31
37
After making the change, run `terraform plan`, inspect the output to ensure it looks as you expect, then run `terraform apply`.
38
+
</TabItem>
39
+
<TabItemvalue="Terragrunt"label="Terragrunt">
40
+
41
+
Below is a module block referencing version `0.15.3` of the `single-server` submodule from the `terraform-aws-server` module.
42
+
43
+
To update to version `0.15.4`, you update the value to the right of `ref=` in the source attribute. Since the version number denotes that this update is backwards compatible, it should not require any other changes.
After making the change, run `terragrunt plan`, inspect the output to ensure it looks as you expect, then run `terragrunt apply`.
75
+
76
+
</TabItem>
77
+
<TabItemvalue="Terragrunt with _envcommon"label="_envcommon (Terragrunt)">
78
+
79
+
When following the `_envcommon` pattern, there are two places that reference the git tag created by the release — the `.hcl` file with the reference to the module in the `_envcommon` directory and the environment and region specific references to the _envcommon file.
80
+
81
+
Below is an example using the `_envcommon` pattern to reference version `0.15.3` of the `single-server` submodule from the `terraform-aws-server` module. To update to version `0.15.4`, you update the value to the right of `ref=` in the source attribute. Since the version number denotes that this update is backwards compatible, it should not require any other changes.
0 commit comments