Many thanks for sharing your space at the last Off...
# office-hours
r
Many thanks for sharing your space at the last Office Hours, @Erik Osterman (Cloud Posse) et al, genuinely appreciate the time. I brought a fair few Qs about Terraform provisioning pipelines with GitHub Action, to which you added plenty of depth and potential pitfalls to look out for. Summarize plan outline • Reviewing 1000s of lines of planned changes is simply not feasible, but a brief 1-liner like "Plan: 2 to add, 2 to change, 2 to destroy" fails to convey the scope of impact. • A "middle-ground" outline would be preferable, which accounts for character limits within PR comments, while linking to the complete output log in the workflow job summary. Plan file reuse with encryption • Too often PRs are merged with
apply -auto-approve
, which is optimistic at best, but liable to configuration drift from changes made outside the workflow. • While it's best practice to reuse the plan file from
plan
command, storing and retrieving it between workflow runs isn't easy, let alone if it contains sensitive data. Apply before OR after merge • Whenever we choose to apply changes, we need a way to uniquely identify and fetch the appropriate plan file outside of
pull_request
context. • In addition to
push
and
pull_request_target
events, support GitHub's native merge queue feature to conditionally merge the PR only if it applies successfully. As promised, I managed to wrangle out a few hours over the weekend to pour over these problems, and address each one in turn. Drawn up my progress in a blog post—happy to share, if you'd like? (keen to not fall foul of any self-promotion rules!)
e
That would be great
Please share
r
Here's the blog post with announcement/highlights, And the actual GitHub Action itself: TF-via-PR. When you have a moment, would really appreciate your thoughts/feedback, especially once you've seen the 4 example workflows showcasing common use cases.
sweetops 2
👍🏾 1
👀 1