Skip to content

Commit 4666df9

Browse files
authored
fix docs (#2096)
1 parent 0e8db99 commit 4666df9

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/ce/howto/custom-commands.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -54,10 +54,10 @@ workflows:
5454
- run: terraform plan -input=false -refresh -no-color -out $DIGGER_PLANFILE
5555
```
5656

57-
Note that you need to use the -out flag to write the output to the $DIGGER_PLANFILE env variable, since this will be used in postprocessing steps by digger.
57+
Note that you need to use the -out flag to write the output to the `$DIGGER_PLANFILE` env variable, since this will be used in postprocessing steps by digger.
5858

59-
Similarly for the apply step you can use the $DIGGER_PLANFILE env variable to point to the plan file to apply. Note that this will only work when you have the [plan persistence](/ce/howto/store-plans-in-a-bucket)
60-
configured. If plan persistence is not configured, the $DIGGER_PLANFILE environment variable will not be set during the apply step. Here is an example with both plan and apply commands overriden:
59+
Similarly for the apply step you can use the `$DIGGER_PLANFILE` env variable to point to the plan file to apply. Note that this will only work when you have the [plan persistence](/ce/howto/store-plans-in-a-bucket)
60+
configured. If plan persistence is not configured, the `$DIGGER_PLANFILE` environment variable will not be set during the apply step. Here is an example with both plan and apply commands overriden:
6161

6262
```
6363
workflows:

0 commit comments

Comments
 (0)