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
@@ -87,7 +86,7 @@ The following workflows showcase common use cases, while a comprehensive list of
87
86
<tr>
88
87
<td>
89
88
</br>
90
-
<a href="/.github/examples/pr_push_auth.yaml"><strong>Run on</strong></a> <code>pull_request</code> (plan) and <code>push</code> (apply) events with Terraform, AWS <strong>authentication</strong> and <strong>caching</strong>.
89
+
<a href="/.github/examples/pr_push_auth.yaml"><strong>Run on</strong></a> <code>pull_request</code> (plan) and <code>push</code> (apply) events with Terraform, <strong>authentication</strong> and <strong>cache</strong>.
91
90
</br></br>
92
91
</td>
93
92
<td>
@@ -99,12 +98,12 @@ The following workflows showcase common use cases, while a comprehensive list of
99
98
<tr>
100
99
<td>
101
100
</br>
102
-
<a href="/.github/examples/pr_push_stages.yaml"><strong>Run on</strong></a> <code>pull_request</code> (plan) and <code>push</code> (apply) events with <strong>conditional job stages</strong> based on plan file.
101
+
<a href="/.github/examples/pr_push_stages.yaml"><strong>Run on</strong></a> <code>pull_request</code> (plan) and <code>push</code> (apply) events with <strong>conditional jobs</strong> based on plan file.
103
102
</br></br>
104
103
</td>
105
104
<td>
106
105
</br>
107
-
<a href="/.github/examples/schedule_refresh.yaml"><strong>Run on</strong></a> <code>schedule</code> (cron) event with <code>-refresh-only</code> to open an issue on <strong>configuration drift</strong>.
106
+
<a href="/.github/examples/schedule_refresh.yaml"><strong>Run on</strong></a> <code>schedule</code> <strong>cron</strong> event with <code>-refresh-only</code> to open an issue on <strong>configuration drift</strong>.
108
107
</br></br>
109
108
</td>
110
109
</tr>
@@ -116,7 +115,7 @@ The following workflows showcase common use cases, while a comprehensive list of
116
115
</td>
117
116
<td>
118
117
</br>
119
-
<a href="/.github/examples/pr_self_hosted.yaml"><strong>Run on</strong></a> <code>pull_request</code> (plan or apply) and <code>labeled</code> <strong>(manual) events on self-hosted</strong> Terraform and OpenTofu.
118
+
<a href="/.github/examples/pr_self_hosted.yaml"><strong>Run on</strong></a> <code>pull_request</code> (plan or apply) and <code>labeled</code> <strong>manual</strong> events on <strong>self-hosted</strong> Terraform/OpenTofu.
120
119
</br></br>
121
120
</td>
122
121
</tr>
@@ -131,7 +130,10 @@ In order to decrypt the plan file locally, use the following commands after down
| Check | `plan-parity` | Replace the plan file if it matches a newly-generated one to prevent stale apply (very rarely needed nowadays).</br>Default: `false`|
156
-
| Security | `plan-encrypt` | Encrypt plan file artifact with the given input.</br>Example: `${{ secrets.PASSPHRASE }}`|
| UI | `label-pr` | Add a PR label with the command input (e.g., `tf:plan`).</br>Default: `true`|
161
+
| UI | `comment-pr` | Add a PR comment: `always`, `on-change`, or `never`.<sup>4</sup></br>Default: `always` |
162
+
| UI | `comment-method` | PR comment by: `update`existing comment or `recreate` and delete previous one.<sup>5</sup></br>Default: `update` |
163
+
| UI | `tag-actor` | Tag the workflow triggering actor: `always`, `on-change`, or `never`.<sup>4</sup></br>Default: `always` |
164
+
| UI | `hide-args` | Hide comma-separated list of CLI arguments from the command input.</br>Default: `detailed-exitcode,lock,out,var=`|
165
+
| UI | `show-args` | Show comma-separated list of CLI arguments in the command input.</br>Default: `workspace`|
164
166
</br>
165
167
166
-
The default behavior of `comment-method` is to update the existing PR comment with the latest plan/apply output, making it easy to track changes over time through the comment's revision history.</br>
167
168
168
-
[](https://raw.githubusercontent.com/op5dev/tf-via-pr/refs/heads/main/.github/assets/revisions.png "View full-size image.")
169
+
- <sup>1</sup> Both `command: plan` and `command: apply` include: `init`, `fmt` (with `format: true`), `validate` (with `validate: true`), and `workspace` (with `arg-workspace`) commands rolled into it automatically.</br>
170
+
To separately run checks and/or generate outputs only, `command: init` can be used.</br>
171
+
- <sup>2</sup> For `merge_group` event trigger, `plan-parity: true` inputs helps to prevent stale apply within the merge queue of workflow runs.</br>
172
+
- <sup>3</sup> The secret string input for `plan-encrypt` can be of any length, as long as it's consistent between encryption (plan) and decryption (apply).</br>
173
+
- <sup>4</sup> The `on-change` option is true when the exit code of the last TF command is non-zero.</br>
174
+
- <sup>5</sup> The default behavior of `comment-method` is to update the existing PR comment with the latest plan/apply output, making it easy to track changes over time through the comment's revision history.</br>
175
+
176
+
[](https://raw.githubusercontent.com/op5dev/tf-via-pr/refs/heads/main/.github/assets/revisions.png "View full-size image.")
0 commit comments