Daniel Flook
Daniel Flook
Terraform plan for __test-apply apply_user_token__ Plan: 1 to add, 0 to change, 0 to destroy. Changes to Outputs. ```hcl Terraform used the selected providers to generate the following execution plan....
Hello @aywengo, can you explain what you would use this for?
Is it possible the change was applied before the proper apply job was run? (assuming that the lambda package changes every time/was changed externally).
Hi @JafoFett, you should be able to select whatever the apply job is as a required status check. This would require that the apply job was triggered and ran successfully...
Hello @MatiasNielsen, do you no longer get an TERRAFORM_HTTP_CREDENTIALS error?
It looks like you could use [this action](https://github.com/marketplace/actions/reviews-counter) to get the number of approving reviews. Edit: That only works for pull_request & pull_request_review events, not issue_comment, so that won't work...
I don't see any problems with that workflow, what happens when it runs? Do you see the plan in the workflow log, or does the job fail entirely?
Any existing comment is updated with the new plan. If the plan hasn't changed it may be hard to tell - check the build number in the comment and the...
The comment is always kept up to date with an accurate plan. I'm not sure how useful keeping outdated plans around would be.
I would expect the existing comment to be updated to say 'Plan applied in Job #xxx'