Rishav
10/21/2024, 1:41 AMapply -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!)Erik Osterman (Cloud Posse)
10/21/2024, 5:43 PMErik Osterman (Cloud Posse)
10/21/2024, 5:43 PM