-
Notifications
You must be signed in to change notification settings - Fork 115
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[.github] - refacto: specify deploy region (#9276)
* [k8s] - feature: support regional specification for cloud builds - Added a --region flag to specify the region during cloud builds - Cloud build configuration now requires the --region parameter to operate correctly - Docker image tags are now constructed using the provided region value * [.github] - feature: allow regional deployment options for front edge workflow - Added input fields for specifying deployment regions with default region as 'us-central1' - Split the build-and-deploy job into separate notify, build, and deploy jobs for better modularity - Implemented matrix strategy for build job to handle multiple regions - Adjusted notify and deployment steps to use dynamic region input and pass messages correctly with thread timestamps * [github/workflows] - feature: specify deployment region for services - Add the `--region` parameter with `us-central1` to deployment commands across multiple GitHub Actions workflows - Ensure consistency and correct regional deployment for the services `alerting-temporal`, `connectors`, `core`, `dante`, `front-qa`, `front`, `nginx`, `oauth`, `prodbox`, and `viz` * [.github] - refactor: streamline deployment workflow for front-edge - Removed regional deployment options in favor of a single fixed region deployment - Merged build and deployment steps into a single job to simplify the workflow - Updated Slack notification steps to reflect the changes in job structure - Set the deployment region to 'us-central1' as a default without options - Removed redundant checks-outs and extractions of the git short SHA - Fixed Slack notification to use the thread timestamp from the current job * [.github/workflows] - feature: refactor deploy-prodbox workflow with new regions and notification steps - Add input for regions with a choice type enabling selection of deployment regions - Implement notification step that outputs thread timestamp for Slack notification - Separate build and deployment jobs for better modularity - Introduce a condition to set regions based on user input, supporting 'all' option - Modify build step to iterate over regions and include region in build step name - Update slack-notify step to use thread timestamp from notify-start job - Streamline input of regions to the trigger-component-deploy step * [.github] - feature: specify deployment region in deploy-front-edge workflow - Added the `--region` flag to deployment command to target `us-central1` for deployment operations * [.github/workflows] - refactor: update deployment workflows for front-edge and prodbox - Modify the deploy-front-edge.yml workflow to support multiple regions and notify separately for build start - Adjust the deploy-front-edge.yml to use a matrix strategy for building images across specified regions - Simplify the deploy-prodbox.yml by removing the region input and hardcoding the region for deployment - Consolidate steps in deploy-prodbox.yml, removing the separate notifications for build start and merging build and deploy steps
- Loading branch information
1 parent
b713077
commit 4cfca02
Showing
13 changed files
with
72 additions
and
27 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters