generate_github_actions_file

Generate GitHub Actions workflows by providing an ENV_NAME to automatically substitute environment-specific values like DOCKER_REPO and KUBE_CONFIG_SECRET. The tool reads Azure and GCP templates, constructs multi-step CI/CD pipelines, and writes the final YAML file directly to .github/workflows/{ENV_NAME}.yaml.

You can substitute environment-specific values including ENV_NAME, DOCKER_REPO, and KUBE_CONFIG_SECRET in your GitHub Actions CI/CD pipeline. The template-based generation applies these variables to Azure AKS or GCP GKE templates, ensuring consistent configuration across new deployment environments.

Yes, you can automate GitHub Actions workflow creation for multiple environments like staging and production. By providing a specific ENV_NAME for each target, the tool performs environment-specific substitutions and generates a dedicated, ready-to-run YAML workflow file for repeatable deployments.

The generated GitHub Actions YAML file is saved directly to the .github/workflows/ directory in your repository. It is written as .github/workflows/{ENV_NAME}.yaml, using the environment name you provided to ensure deterministic CI/CD pipeline setup.

Yes, this workflow generation tool supports both Azure AKS and GCP GKE templates. It reads from these references to construct multi-step CI/CD pipelines, allowing teams to switch between Azure and GCP deployments with minimal changes to the environment-specific substitutions.