A blog site on our Real life experiences with various phases of DevOps starting from VCS, Build & Release, CI/CD, Cloud, Monitoring, Containerization.
Starting the blog with the question – What is Terraform?
It can be called a magic wand that creates Infrastructure on the basis of the code that you write.
In Hashicorp’s words, “Terraform is an open-source Infrastructure as A Code software tool that enables you to safely and predictably create, change, and improve infrastructure.“
Continue reading “Terraform Version Upgrade”Let’s consider a scenario in which you are deploying your infrastructure using a Terraform code (infrastructure-as-code) which is stored in a remote git repository. Now working in an organization you need to make sure that all your deployments are always tracked without an exception, an add-on to that whether your Terraform code is following your security and compliance policies or not. Or maybe what is the monthly cost that you can expect with that infra and whether it lies under your budget or not. You may also want to take note that all your resources are being created in the same region… etc… etc.
Sounds magical right !!! We all know that these concerns are very important when you’re looking for a highly consistent, fully tracked, and automated approach. That’s why in this article we are going to look for a simple step-by-step way to automate and streamline our Terraform code using Azure DevOps (ADO).
Why DevOps Rides on Immutable Infrastructure? The acceptance of “immutable infrastructure” has emerged as a viable way to improve DevOps processes and culture. By introducing standardisation in application deployment and management, the immutable infrastructure helps, among other things, to foster a better collaborative environment among developers, operations, and other stakeholders.
Let’s discuss a bit about Immutable Infra and the benefits which it brings to the table. Once we have a better understanding of it, we’ll really start to see the use case in our Deployments Model.
Continue reading “Provisioning Infra and Deployments In AWS : Using Packer, Terraform and Jenkins”Codeherent was founded in the year 2016 by the founding team after they met in Alacrity Foundation, a UK entrepreneurship course, in 2015. The founding team’s main focus was how to improve DevOps with a fast Infrastructure as Code (IaC) review process.
The tool is singularly focused on Terraform and is helping multiple organizations to understand, optimize and review their Cloud Infrastructure in a diagrammatic manner. They recognize the fact that organizations are clambering for DevOps maturity, GitOps centralization, and infrastructure agility. Abstracting IaC into an interactive diagram removes the complexity and helps us all to keep moving forward quickly.
Continue reading “Codeherent: Automatic Cloud Diagrams Powered by Terraform”
We often face complications after a certain point when we can not change the foundation layer of our code because we haven’t thought it through and didn’t plan or strategize the way of writing code in the beginning, there are certain points which should be taken under consideration similarly there are some common mistakes which we should avoid.
