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: content/blog/terragrunt-envs-management.md
+17Lines changed: 17 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -126,6 +126,23 @@ Here is a high-level overview of the terragrunt workflow:
126
126
127
127
> We run the command `terragrunt run-all plan` in the root directory.
128
128
129
+
Output
130
+
131
+
```bash
132
+
22:03:23.710 INFO The stack at . will be processed in the following order forcommand plan:
133
+
Group 1
134
+
- Module .
135
+
- Module ./production/app
136
+
- Module ./production/database
137
+
- Module ./production/redis
138
+
- Module ./qa/app
139
+
- Module ./qa/database
140
+
- Module ./qa/redis
141
+
- Module ./staging/app
142
+
- Module ./staging/database
143
+
- Module ./staging/redis
144
+
```
145
+
129
146
This will run the terragrunt plan in each sub directory it finds, Then it reads the `terragrunt.hcl` file in the current directory and does the following:
130
147
131
148
1. Terragrunt reads the `terraform` block and downloads the specified Terraform module
0 commit comments