🏗️ dev TF deployment to Cloud.gov

[jadudm]

At a glance

In order to test my work
as a developer
I want a dev environment

We want to be able to deploy the application to three distinct environments in Cloud.gov.

• dev
• staging
• prod

This ticket sets us up for achieving this target through iteration.

Acceptance Criteria

Our first goal will be to have a deployment that any developer or team member can trigger at any time.

We want...

Preview Give feedback

1. a GH action for triggering a deployment to dev from main
2. secrets are managed via GH secrets
3. the full app deployed to the dev space in CF/Cloud.gov

Shepherd

• Engineering shepherd: @jadudm

Background

Our goal is to have

• dev deployable on every push to main
• staging be a daily deploy, with E2E tests, and
• prod be able to be triggered by GH action

We will not automate prod pushes at this time

Security Considerations

Required per CM-4.

The TF should be clean. Access controls should be in place via GH teams, and our CF access controls via static file in the repository.

---

Process checklist

• Has a clear story statement
• Can reasonably be done in a few days (otherwise, split this up!)
• Shepherds have been identified
• UX youexes all the things
• Design designs all the things
• Engineering engineers all the things
• Meets acceptance criteria
• Meets QASP conditions
• Presented in a review
• Includes screenshots or references to artifacts
• Tagged with the sprint where it was finished
• Archived

If there's UI...

• Screen reader - Listen to the experience with a screen reader extension, ensure the information presented in order
• Keyboard navigation - Run through acceptance criteria with keyboard tabs, ensure it works.
• Text scaling - Adjust viewport to 1280 pixels wide and zoom to 200%, ensure everything renders as expected. Document 400% zoom issues with USWDS if appropriate.