setup_new_deployment

To automate end-to-end deployment environment setup, you provide environment names and domains to generate Git branches, Kubernetes manifests, and GitHub Actions workflows. This orchestrates provisioning by deriving standard configurations without executing cluster commands directly.

New environment onboarding requires providing ENV_NAME, API_DOMAIN, and CALL_DOMAIN. These parameters initialize the setup, which derives standard values to generate Git branches, Kubernetes manifests, and GitHub Actions workflows for the specified environment.

No, this deployment automation does not execute Kubernetes cluster commands directly. It generates manifests and workflows, then delivers a guide containing the necessary secrets and cluster commands for you to apply manually within your environment.

Yes, you can generate GitHub Actions workflows for multiple environments like staging and production. The setup scales by deriving environment-specific configurations and secrets based on the initial parameters you provide for each target environment.

The best way to ensure consistent Git branch and manifest generation is to automate the end-to-end deployment environment setup. This enforces project conventions for branches, manifests, and CI definitions across all newly provisioned environments.