https://pavanyara.com/tags/infrastructure/Recent content in Infrastructure on Pavan YaraHugo -- gohugo.ioen-USpavan.yara@gmail.com (Pavan Yara)pavan.yara@gmail.com (Pavan Yara)Pavan YaraWed, 19 Dec 2018 21:49:09 +0530https://pavanyara.com/blog/lessons-from-writing-infra-code/Wed, 19 Dec 2018 21:49:09 +0530pavan.yara@gmail.com (Pavan Yara)https://pavanyara.com/blog/lessons-from-writing-infra-code/<p>Original post up at <a href="https://blog.gruntwork.io/5-lessons-learned-from-writing-over-300-000-lines-of-infrastructure-code-36ba7fadeac1">Gruntwork blog</a></p> <ol> <li>Go through the <a href="https://cdn-images-1.medium.com/max/2000/1*-nYI19LZZKDQjdAx0qhlFw.png">Production-Grade Infrastructure Checklist</a> to make sure you’re building the right thing.</li> <li>Define your infrastructure as code using tools such as Terraform, Packer, and Docker. Make sure your team has the time to master these tools (see DevOps Resources).</li> <li>Build your code out of small, standalone, composable modules (or use the off-the-shelf modules in the Infrastructure as Code Library).</li> <li>Write automated tests for your modules using Terratest.</li> <li>Submit a pull request to get your code reviewed.</li> <li>Release a new version of your code.</li> <li>Promote that new version of your code from environment to environment.</li> </ol>Original post up at Gruntwork blog

1. Go through the Production-Grade Infrastructure Checklist to make sure you’re building the right thing.
2. Define your infrastructure as code using tools such as Terraform, Packer, and Docker. Make sure your team has the time to master these tools (see DevOps Resources).
3. Build your code out of small, standalone, composable modules (or use the off-the-shelf modules in the Infrastructure as Code Library).
4. Write automated tests for your modules using Terratest.
5. Submit a pull request to get your code reviewed.
6. Release a new version of your code.
7. Promote that new version of your code from environment to environment.

]]>