Andriy Knysh is a Certified AWS Specialist, Java Developer, and Cloud Architect. He’s the Terraform genius responsible for maintaining most of our modules. (Miami, Florida)
Description of the recommended workflow and division of responsibility to use when creating and deploying new Terraform code
HCL is HashiCorp’s configuration language used in multiple products, but most notably in terraform.
If not using something like Atlantis, we’ve seen others use Codefresh and Jenkins.
Igor Rodionov is a Sr DevOps Engineer. He’s a Kubernetes expert, Helm Chart maestro, GoLang Developer, and Beanstalk Slinger.
Infrastructure as Code (IaC) is the process of managing/provisioning Infrastructure as a Service (IaaS) using machine-readable definition files (usually DSLs), rather than rely on humans doing physical/manual hardware configuration.
Make sure that your GitHub SSH public key has been added to your geodesic ssh-agent
This is normally an issue with a bad aws-vault session
Use Git Workflow Infrastructure as Code Infrastructure as Code is essential for managing change control and as a system of record for disaster recovery. Configuration is a form of Intellectual Property. Without the code, you don’t own the IP. Feature Branches Recommend using a consistent naming convention for branch names by all developers. Using a convention will help developers to navigate branches. Pull Requests Pull Requests should express ## what changed and ## why it changed (e.
Collection of Terraform Root Module invocations