Workflows created for Terragrunt Plan and Deploy.
Workflows created for Terragrunt Plan and Deploy.
Change Summary
This update introduces two new GitHub Actions workflows for deploying and planning infrastructure using Terragrunt. Additionally, it updates the Kubernetes provider configuration and specifies tool versions in mise.toml.
Technical Details
- Workflows:
deploy.yml: Automates the deployment of infrastructure using Terragrunt. It includes steps for checking out code, validating HCL, configuring AWS credentials, and executingterragrunt apply.plan.yml: Automates the planning phase for infrastructure changes. It includes similar steps but executesterragrunt planinstead.
- Kubernetes Provider Configuration:
- Updated
kube.hclto specify the Kubernetes API server host.
- Updated
- Tool Versions:
- Added
mise.tomlto pin Terragrunt and OpenTofu versions.
- Added
Key Learnings & Insights
- Automation: The introduction of GitHub Actions workflows streamlines the deployment and planning processes, reducing manual intervention.
- Configuration Management: Specifying the Kubernetes API server host in
kube.hclenhances configuration clarity and maintainability. - Tool Versioning: Pinning tool versions in
mise.tomlensures consistency across development environments.
Impact Assessment
- Efficiency: Automated workflows improve deployment efficiency and reduce the risk of human error.
- Maintainability: Clear configuration and tool versioning enhance code maintainability and reproducibility.
- Security: Using GitHub Secrets for sensitive information (e.g., AWS credentials, Tailscale auth key) improves security posture.
Developer Notes
- Gotchas: Ensure all required secrets are configured in the GitHub repository settings.
- Future Improvements: Consider adding additional checks or notifications to the workflows for enhanced monitoring.
This post is licensed under CC BY 4.0 by the author.