Modify Cloud Build Configuration for Tagged Release and Separate Production/Development Environments

[sunank200]

• [x] Add deployment story for Ask-Astro.
• [x] Modify the Cloud Build configuration to build and deploy only when a tagged release is pushed to GitHub and to separate the setup for production and development environments.

Steps to Implement:

Create distinct Cloud Build configuration files for production and development, named cloudbuild-prod.yaml and cloudbuild-dev.yaml respectively.

Configure GitHub triggers for tagged releases in both configurations, ensuring they correspond to their respective environments.

Implement conditional logic within each configuration file to determine whether a build and deployment should proceed based on branch and tag information.

Outcome:

• [x] This setup ensures that builds and deployments are initiated solely when tagged releases are pushed to GitHub. The correct configuration file is automatically selected based on the activated trigger, allowing environment-specific substitutions and configurations to be applied.

Additional Context:

This change enhances deployment control and separates production and development workflows, improving overall project management.

[sunank200]

Deployments:

• cloud build: https://console.cloud.google.com/cloud-build/triggers;region=global?project=ask-astro
• cloud run: https://console.cloud.google.com/run?referrer=search&project=ask-astro

[sunank200]

@pankajastro when setting up or editing the Cloudflare Pages project, we can specify the branch to deploy. However, I could not find a way for Cloudflare Pages to support deployments based only on tags directly from its UI.

So this is what we require: we can have release branch for prod deployment and dev branch can be on main and non-prod branches. WDYT?

[sunank200]

We have created a Slack app in a private account and tested this implementation and this app works fine.

Also, we have created a release branch for prod.

PR: https://github.com/astronomer/ask-astro/pull/46