TF DB changes

[alismx]

This will be pushed out at the beginning of 2024

DEVOPS PULL REQUEST

Cases not yet handled

• DB pw has been updated, but API doesn't report healthy. Slots would not swap, but the db pw would have already been updated. Solution: Write an action to revert pw updates to db before exiting the deployment.

Related Issue

• Why is this being done? Link to issue, or a few sentences describing why this PR exists

Changes Proposed

• Downtime measured during testing was between 1m32s and 3m6s. It should stick to the lower end because the database password update process wasn't as optimized during the test where it took 3m6s.

Additional Information

• decisions that were made
• notice of future work that needs to be done

Testing

• How should reviewers verify this PR?

Checklist for Primary Reviewer

Infrastructure

• Consult the results of the terraform-plan job inside the "Terraform Checks" workflow run for this PR. Confirm that there are no unexpected changes!

Security

• Changes with security implications have been approved by a security engineer (changes to authentication, encryption, handling of PII, etc.)
• Any dependencies introduced have been vetted and discussed

Cloud

• Oncall has been notified if this change is going in after-hours
• If there are changes that cannot be tested locally, this has been deployed to our Azure test, dev, or pentest environment for verification

Documentation

• Any changes to the startup configuration have been documented in the README

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[alismx]

Closing this for now