-
Notifications
You must be signed in to change notification settings - Fork 53
How to Review and Test Pull Requests with Terraform Changes
fzhao99 edited this page May 21, 2024
·
1 revision
- Select Details to the right of Terraform Checks / check-terraform-formatting (pull_request)
- Select terraform-plan on the left, then select Terraform Plan Prod to look at the resources that will be modified for the PR
- This is the key for Terraform actions, these symbols beside resources will explain the actions that will be applied once the
terraform apply
command is ran
-
While reviewing the terraform plan, ensure the resources modified match the resources the PR owner identified in the PR Testing section
- For example in the Testing Section of the PR,
module.app_gateway.azurerm_application_gateway.load_balancer
should be updated in place
- For example in the Testing Section of the PR,
- Search for the module in the logs and you will see this matches the PR testing section so this resources change has been verified
- If there is a resource modification that was not identified in the PR Testing section, annotate this in your PR comments so the owner can double check that this is not an unintentional change that was introduce with the code
- go to the app service in Azure
- click networking
- Visit IP labeled
Inbound Address
, it should result in a 404.
Additionally, on the same networking page:
- click the link for the
Public network access
which will take you to theAccess Restrictions
- Check that we only allow access from that environments load balancer.
dev3 was used for this smoke test
-
Open up the simplereportdev3app storage account "Queues"
- Have fhir-data-publishing and test-event-publishing queues open
-
Go to https://dev3.simplereport.gov/app/queue and submit a single entry test with COVID and Flu result
-
Check both queues to see there is a message in the expected format/shape. (Example of a message from a test submission):
- Getting Started
- [Setup] Docker and docker compose development
- [Setup] IntelliJ run configurations
- [Setup] Running DB outside of Docker (optional)
- [Setup] Running nginx locally (optional)
- [Setup] Running outside of docker
- Accessing and testing weird parts of the app on local dev
- Accessing patient experience in local dev
- API Testing with Insomnia
- Cypress
- How to run e2e locally for development
- E2E tests
- Database maintenance
- MailHog
- Running tests
- SendGrid
- Setting up okta
- Sonar
- Storybook and Chromatic
- Twilio
- User roles
- Wiremock
- CSV Uploader
- Log local DB queries
- Code review and PR conventions
- SimpleReport Style Guide
- How to Review and Test Pull Requests for Dependabot
- How to Review and Test Pull Requests with Terraform Changes
- SimpleReport Deployment Process
- Adding a Developer
- Removing a developer
- Non-deterministic test tracker
- Alert Response - When You Know What is Wrong
- What to Do When You Have No Idea What is Wrong
- Main Branch Status
- Maintenance Mode
- Swapping Slots
- Monitoring
- Container Debugging
- Debugging the ReportStream Uploader
- Renew Azure Service Principal Credentials
- Releasing Changelog Locks
- Muting Alerts
- Architectural Decision Records
- Backend Stack Overview
- Frontend Overview
- Cloud Architecture
- Cloud Environments
- Database ERD
- External IDs
- GraphQL Flow
- Hibernate Lazy fetching and nested models
- Identity Verification (Experian)
- Spring Profile Management
- SR Result bulk uploader device validation logic
- Test Metadata and how we store it
- TestOrder vs TestEvent
- ReportStream Integration
- Feature Flag Setup
- FHIR Resources
- FHIR Conversions
- Okta E2E Integration
- Deploy Application Action
- Slack notifications for support escalations
- Creating a New Environment Within a Resource Group
- How to Add and Use Environment Variables in Azure
- Web Application Firewall (WAF) Troubleshooting and Maintenance
- How to Review and Test Pull Requests with Terraform Changes