-
Notifications
You must be signed in to change notification settings - Fork 53
Deploy Application Action
alismx edited this page Apr 5, 2023
·
2 revisions
The deployment process involves promoting API from the secondary slot to production, verifying its readiness, and deploying the client/frontend application to Azure storage. The process ensures the application is fully operational and available to end users.
This action requires the following inputs:
- deploy-env: The environment being deployed (e.g. "prod", "dev" or "demo"). This input field is mandatory.
- client-tarball: The path to the tar file containing the client code to deploy. This input field is mandatory.
uses: ./.github/actions/deploy-application
with:
deploy-env: 'dev'
client-tarball: 'client.tgz'
The action runs the following steps:
-
Unpack client
: Unpacks the client code from the tarball. -
Promote API to production and verify that it is ready
: Promotes the API to production and verifies its readiness for deployment using make commands. -
Check for production app readiness
: Checks if the production app is ready for deployment. -
Deploy frontend app
: Deploys the frontend app by uploading the client code to Azure Blob Storage.
This action has no outputs.
- 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