Skip to content

Commit 87c2001

Browse files
committed
Add missing init step in using-the-library
1 parent bcb177e commit 87c2001

File tree

2 files changed

+43
-1
lines changed

2 files changed

+43
-1
lines changed

_docs-sources/library/usage/using-the-library.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -222,6 +222,27 @@ For this guide, we'll run `terraform plan` and `terraform apply` locally. We rec
222222

223223
:::
224224

225+
### Init
226+
227+
Before you can run a `plan` or `apply`, you need to run an `init`, which performs a series of initialization steps to prepare the working directory for use with Terraform.
228+
229+
<Tabs groupId="tool-choice">
230+
<TabItem value="Terraform" label="Terraform" default>
231+
232+
```bash
233+
terraform init
234+
```
235+
236+
</TabItem>
237+
<TabItem value="Terragrunt" label="Terragrunt" default>
238+
239+
```bash
240+
terragrunt init
241+
```
242+
243+
</TabItem>
244+
</Tabs>
245+
225246
### Plan
226247

227248
Now that you have created a module and a reference that is specific to a single environment and AWS region, you can run a `plan` to see the infrastructure resources that will be provisioned by the module.

docs/library/usage/using-the-library.md

Lines changed: 22 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -222,6 +222,27 @@ For this guide, we'll run `terraform plan` and `terraform apply` locally. We rec
222222

223223
:::
224224

225+
### Init
226+
227+
Before you can run a `plan` or `apply`, you need to run an `init`, which performs a series of initialization steps to prepare the working directory for use with Terraform.
228+
229+
<Tabs groupId="tool-choice">
230+
<TabItem value="Terraform" label="Terraform" default>
231+
232+
```bash
233+
terraform init
234+
```
235+
236+
</TabItem>
237+
<TabItem value="Terragrunt" label="Terragrunt" default>
238+
239+
```bash
240+
terragrunt init
241+
```
242+
243+
</TabItem>
244+
</Tabs>
245+
225246
### Plan
226247

227248
Now that you have created a module and a reference that is specific to a single environment and AWS region, you can run a `plan` to see the infrastructure resources that will be provisioned by the module.
@@ -402,6 +423,6 @@ Finally, consider how else you might test your module. Are there additional succ
402423
<!-- ##DOCS-SOURCER-START
403424
{
404425
"sourcePlugin": "local-copier",
405-
"hash": "9bce4eb133294e715753e319b3750cfa"
426+
"hash": "a716579681d6f9b3880dc9df0e6e9e25"
406427
}
407428
##DOCS-SOURCER-END -->

0 commit comments

Comments
 (0)