-
Notifications
You must be signed in to change notification settings - Fork 53
How to Add and Use Environment Variables in Azure
Alis Akers edited this page Jan 8, 2024
·
2 revisions
The following steps will create an Azure-based environment variable and automatically make it available in each environment when the application is deployed.
- Add desired secrets to
simple-report-global
in Azure Key Vault. Make sure to affix-${env}
to the name - In
ops/${env}/_data.tf
in each respective environment folder, add a data entry with the secret’s name in Key Vault - In
ops/${env}/api.tf
in each respective environment folder, add an environment variable to app_settings that points to the corresponding entry in that environment's_data.tf
(the file you changed in step 2!). - (Optional) Add an entry to
application.yaml
that refers to the newly-created environment variable from step 3. This is only necessary if you need to override the variable: for example, when leveraging a local environment.
The newly created variable can be accessed in any desired manner that is supported by the code. For example, leveraging the @Value
or @ConfigurationProperties
annotations is a useful approach for the backend Spring application.
- 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