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/ce/howto/custom-commands.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,10 +54,10 @@ workflows:
54
54
- run: terraform plan -input=false -refresh -no-color -out $DIGGER_PLANFILE
55
55
```
56
56
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.
58
58
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:
0 commit comments