Replies: 1 comment 2 replies
-
Hey @NICDzz, let's see if I understand the requirement.
If that sounds about right, then this example workflow should meet your needs, wherein we split op5dev/tf-via-pr into Here's another relevant workflow example where op5dev/tf-via-pr is called twice in the same job, along with TFLint steps in between for format/validation. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
Thanks for a great action plugin :-)
Are there any examples of how to split the plan and push into two separate jobs?
E.g. I want to run the "plan" as part of a validation process and then later on in my workflow (if everything succeeds) use the plan generate with a "fresh" push. Something like:
job1:
- name: Plan TF
uses: op5dev/tf-via-pr@v13
with:
working-directory: ./Terraform
command: plan
arg-lock: false
plan-encrypt: ${{ secrets.PASSPHRASE }}
job2, job3, job4....
job5:
- name: Provision TF
uses: op5dev/tf-via-pr@v13
with:
working-directory: ./Terraform
command: push
arg-lock: true
plan-encrypt: ${{ secrets.PASSPHRASE }}
Beta Was this translation helpful? Give feedback.
All reactions