capturing my experience with everything devopsy
This note is a short addition to the last post -CI/CD of Terraform workspace with YAML-based Azure Pipelines. At the end of that article, I mentioned a few alternate routes regarding YAML-based Azure Pipelines, which I will be covering here. So that we are on the same page, I broke down the build pipeline into … Continue reading YAML based Azure Pipeline approach for CI/CD of Terraform workspace
This note focuses on using Azure DevOps with Terraform workspace to automate the ideas discussed in the previous two notes (i) CI/CD using Terraform and Azure Pipelines -ideation and (ii) Terraform workspace with multiple AWS accounts. If you are new to Azure DevOps, I would suggest you familiarize yourself with either Azure DevOps build and … Continue reading CI/CD of Terraform workspace with YAML based Azure Pipelines
My objectives was to use Terraform to provision resources across environments in the AWS cloud infrastructure. Following a typical CI/CD model, my idea was to build once and deploy multiple. Since there was nothing to build in terraform, I wanted to make sure the same terraform code was applied across all environments. So I thought, … Continue reading Terraform workspace with multiple AWS accounts
After writing a few notes on "Azure DevOps and Terraform," I thought of exploring the idea of integrating Azure DevOps and Terraform a little further. Generally speaking, in Azure Pipelines (classic editor), a build definition (pipeline in Azure DevOps services) is used to compile and package an artifact. Then, under Releases, we have a release … Continue reading CI/CD using Terraform and Azure Pipelines -ideation
Generally speaking, when we work with Terraform to provision resources in AWS Cloud, we have a few pre-requisites. These are -a remote backend to store the Terraform state file, a lock table, and IAM user credentials that Terraform will require to provision the resources. I say "generally speaking" because you can get away with the … Continue reading Create Terraform pre-requisites for AWS using AWS CLI in 3 easy steps
Any Terraform project configuring resources in Azure has pre-requisites. These are (i) a storage account, a container in the storage account, and the access key to the storage account, and (ii) a service principal credential to be able to communicate with Azure to create-update-delete resources. In this post, I describe the process to set up … Continue reading Create Terraform pre-requisites for Azure using Azure CLI in 3 easy steps
This note is in continuation to the previous one -Terraform Remote State -Part1: Using AWS, where I've covered the what and how of a terraform remote state. So that we are all on the same page, I'll list down a few important points related to that: -the current state of infrastructure as referred to by … Continue reading Terraform Remote State -Part 2: Using Azure
When I started learning Terraform, I installed the tool, wrote Terraform configuration files, and ran the commands from my local (laptop). I did not put a lot of thought into understanding a remote state and how it is useful. As I continued learning, and as I started using Azure DevOps to automate infrastructure provisioning using … Continue reading Terraform Remote State -Part 1: Using AWS
As of this writing [Feb 2021], if you've used the Terraform extension from Microsoft DevLabs, you'd have noticed that there is support for only a small set of Terraform commands out of the box. These are "init", "validate", "plan", "validate and apply", and "destroy". But Terraform has many commands: fmt, import, output, show, taint, workspace, … Continue reading Exploring Azure Pipelines, Terraform, and Powershell
In my previous note, [Azure DevOps and Terraform to provision AWS S3], I listed in detail the steps to be followed to provision an S3 bucket using Azure DevOps and Terraform. I referred to the classic editor in the build definition/azure pipelines. Build and release definitions declared via a classic editor in Azure DevOps, although … Continue reading Azure Pipelines (YAML) and Terraform to provision AWS S3
