stateless (terraform) deployments to cloud.gov

[jadudm]

Problem

We want deployments to be repeatable and automated.

How did we discover this problem?

The previous search deployment involved a combination of 1) manual and automated steps, using 2) a combination of deployment tools. This made it difficult for one person to push a button and get a reliable and repeatable deploy.

Job Story(s)

When I press the deploy button in GH Actions, I want to sit back and drink coffee so I can watch my deployment TV.

What are we planning to do about it?

We will be deploying to Cloud.gov. We should get dev working first, and get our S3 sync/access controls in place. Then, we can do prod, and then staging last.

What are we not planning to do about it?

We're... not planning on not doing it.

How will we measure success?

Tasks

Preview Give feedback

1. Access control to Cloud.gov managed via a static file in GH #56
   +0
2. 🏗️ dev TF deployment to Cloud.gov #49
   0 of 3
   +0
3. Automate the dev deploys on every push to main
4. TF state stored in an S3 bucket
5. Setup TF deploy for prod
6. Allow team members to trigger prod deploys by cutting a release in GH
7. Setup TF deploy for staging
8. Automate the staging deploys as a daily action