Use AWS credentials to deploy review apps#2507
Conversation
48cdf60 to
eb6a7a0
Compare
|
sarahseewhy
left a comment
There was a problem hiding this comment.
This makes sense, I think.
I only had one curiosity question but it's non-blocking.
b36906b to
e868b6d
Compare
This prevents us attempting to run multiple instance of terraform at the same time. Instead, the current running workflow will complete before the next one starts. Only 1 running and 1 pending workflow is allowed - any further workflows will supercede the pending one.
Instead of running Terraform directly in the GitHub Actions runners, we now trigger AWS CodeBuild projects to handle the deployment and destruction of review apps. This means that the repository no longer needs extensive AWS permissions in GitHub Actions, and the actual available AWS operations are limited.
These fields are automatically added by AWS when creating a task definition. If we don't include them in our task definition, Terraform tries to remove them on every apply, which causes unnecessary changes to the task definition (and thus noise in our Terraform plan output).
1cf2195 to
10c1646
Compare
|
🎉 A review copy of this PR has been deployed! You can reach it at: https://pr-2507.admin.review.forms.service.gov.uk/ It may take 5 minutes or so for the application to be fully deployed and working. If it still isn't ready For the sign in details and more information, see the review apps wiki page. |
|



What problem does this pull request solve?
Trello card: https://trello.com/c/UIEQ97bl/792-stop-using-self-hosted-runners-on-github
Rather than using a codebuild runner to deploy the review apps, instead authenticate to AWS with OIDC and deploy them directly.
This depends on alphagov/forms-deploy#1958 being merged first.
Things to consider when reviewing