<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Terraform on amasucci.com</title><link>/tags/terraform/</link><description>Recent content in Terraform on amasucci.com</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 24 Feb 2022 06:32:34 +0100</lastBuildDate><atom:link href="/tags/terraform/index.xml" rel="self" type="application/rss+xml"/><item><title>CICD and IaC - IaC Design a CD Pipeline - Ep.4</title><link>/posts/cicd-and-iac-design-a-pipeline/</link><pubDate>Thu, 24 Feb 2022 06:32:34 +0100</pubDate><guid>/posts/cicd-and-iac-design-a-pipeline/</guid><description>IaC Design a CD Pipeline - CICD and IaC Episode 4 This is the last episode of the miniseries CICD and IaC. In this episode we are going to put everything together and see what’s next.
In the previous episodes This mini series started with the first episode about externalising the terraform configuration using yaml decode and yaml files instead of terraform variables. We discussed the different reasons:
Store configuration in the env (12 factor app) Easier to review and less surprises compared to the overrides mechanisms offered by TF vars Automatic validation Then we saw how to seal our terraform modules with docker.</description></item><item><title>CICD and IaC - Test terraform with terratest in Docker - Ep.3</title><link>/posts/cicd-and-iac-test-terraform-with-terratest/</link><pubDate>Thu, 24 Feb 2022 06:32:34 +0100</pubDate><guid>/posts/cicd-and-iac-test-terraform-with-terratest/</guid><description>Test terraform In this third episode of the miniseries CICD and IaC we are going to see how to test the artifact we created in the previous video.
In the previous episodes In previous episodes (link to the playlist) I showed you how to externalise the terraform configuration using the yamldecode function in terraform and how to create artifacts for terraform code using Docker.
Today we are going to start from where we left, and I am going to create a simple test for our module.</description></item><item><title>CICD and IaC - How to Dockerize Terraform - Ep.2</title><link>/posts/cicd-and-iac-dockerize-terraform/</link><pubDate>Thu, 10 Feb 2022 18:00:34 +0100</pubDate><guid>/posts/cicd-and-iac-dockerize-terraform/</guid><description>Dockerise terraform In this second episode of the miniseries CICD and IaC we are going to see how to create immutable artifacts for our terraform code.
In the previous episode We saw how to externalise the configuration of our terraform code → we moved all our variables in a single variable using terraform structured types. While this is nice, because yaml is more readable than HCL, readability is not the only reason for moving the config/variables outside.</description></item><item><title>CICD and IaC - How to Externalise the terraform configuration - Ep.1</title><link>/posts/cicd-and-iac-externalise-terraform-configuration/</link><pubDate>Thu, 03 Feb 2022 18:00:34 +0100</pubDate><guid>/posts/cicd-and-iac-externalise-terraform-configuration/</guid><description>Externalise Terraform Configuration This article is part of a miniseries. In the miniseries I will show with practical examples how to apply concepts of CI/CD to IaC, we are going to see how to create independent immutable artifacts for our IaC. How to package them and how to test their deployment.
This is for experienced terraform users so I won’t describe the terraform and how it works (let me know if you are interested I can make a miniseries to cover that too).</description></item></channel></rss>