Skip to content

Commit

Permalink
Add demo video to GHA README (#522)
Browse files Browse the repository at this point in the history
* Add demo video to GHA README

* Update README.md

* Update README.md

* Update README.md
  • Loading branch information
derekadombek authored Jan 17, 2025
1 parent 30c2948 commit b2cebd3
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion .github/workflows/README.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
# Github Action workflows for building and deploying ReportVision in a dev environment

https://github.com/user-attachments/assets/31cd1870-d77f-4de1-8ed0-473fedfab8ec

## Prerequisites

You will need to create new App registrations(federated secrets) and Resource Groups in your Azure account for each environment, while also updating the existing `AZURE_CLIENT_ID`, `AZURE_TENANT_ID`, `AZURE_SUBSCRIPTION_ID`, `AZURE_OBJECT_ID` ID's in each Github Environment. Most these ID's are found in each environments App Registration Overview page and Subscriptions Overview page in the Azure Portal. To update these secrets in Github go to Settings > Environments > And select the environment you would like to edit.
Expand Down Expand Up @@ -67,4 +69,4 @@ Unfortunately we never had the opportunity to pilot our amazing product to actua

If we were able to deploy to a centrally hosted system. Our thought would have been to create a `deploy-stage.yml` workflow that is structured and functions very similarly to `deploy-dev.yml`, except it would be triggered off of the `main` branch or Github `tags`. If all staging jobs and tests pass, a `deploy-prod.yml` workflow would then get triggered.

If we were required to deploy to STLT-hosted environments, our plan was going to ensure that all services are containerized and deployed as a container orchestrated system with tooling like Kubernetes. This would make it easier for us to be cloud-agnostic and have the ability to quickly "lift-and-shift" our product into different organizations. If this were to happen, we would had to paradigm shift completely.
If we were required to deploy to STLT-hosted environments, our plan was going to ensure that all services are containerized and deployed as a container orchestrated system with tooling like Kubernetes. This would make it easier for us to be cloud-agnostic and have the ability to quickly "lift-and-shift" our product into different organizations. If this were to happen, we would had to paradigm shift completely.

0 comments on commit b2cebd3

Please sign in to comment.