Skip to main content

 𝐈𝐧-𝐝𝐞𝐩𝐭𝐡 𝐋𝐢𝐟𝐞𝐜𝐲𝐜𝐥𝐞 𝐨𝐟 𝐓𝐞𝐫𝐫𝐚𝐟𝐨𝐫𝐦 (𝐈𝐀𝐂)

1. terraform init

2. terraform fmt

3. terraform validate

4. terraform plan

5. terraform apply


1. 𝐭𝐞𝐫𝐫𝐚𝐟𝐨𝐫𝐦 𝐢𝐧𝐢𝐭

These is first stage of lifecycle where terraform creates files/directory,

a) file 1 

→ 𝐭𝐞𝐫𝐫𝐚𝐟𝐨𝐫𝐦.𝐥𝐨𝐜𝐤.𝐡𝐜𝐥 file, this keeps the record of providers version and helps us to avoid compatibility issues while changing the versions of providers.

→ also, we can update the version from older version using command

𝐭𝐞𝐫𝐫𝐚𝐟𝐨𝐫𝐦 𝐢𝐧𝐢𝐭 -𝐮𝐩𝐠𝐫𝐚𝐝𝐞


b) folder 1 → These folder will have 2 files, first is license file and 2nd is provider.exe file which helps us terraform to interact with REST API 


2. 𝐭𝐞𝐫𝐫𝐚𝐟𝐨𝐫𝐦 𝐟𝐦𝐭

In this phase, it beautifies the file i.e format the file to more readable format


3. 𝐭𝐞𝐫𝐫𝐚𝐟𝐨𝐫𝐦 𝐯𝐚𝐥𝐢𝐝𝐚𝐭𝐞

→ In this phase, it check for any syntax error eg: missing {}, :, : 

→ Since we will be creating a huge infrastructure automation like Onboarding, Provisioning Azure Virtual Machines, Implementing Azure Policy & RBAC.


4. 𝐭𝐞𝐫𝐫𝐚𝐟𝐨𝐫𝐦 𝐩𝐥𝐚𝐧

→In this phase, it gives an overview of what exactly will be done once we execute the plan, example: how many resources will be created, destroyed or changed once we execute the plan will be shown here.


5. 𝐭𝐞𝐫𝐫𝐚𝐟𝐨𝐫𝐦 𝐚𝐩𝐩𝐥𝐲

→In this phase, the actual execution of all the plan happens and terraform will try to create, destroy or change the resources of the given cloud provider, example creating azure resource groups.

→ Here, it also creates a state file, namely 𝐭𝐞𝐫𝐫𝐚𝐟𝐨𝐫𝐦.𝐭𝐟𝐬𝐭𝐚𝐭𝐞.𝐛𝐚𝐜𝐤𝐮𝐩 𝐟𝐢𝐥𝐞 & 𝐭𝐞𝐫𝐫𝐚𝐟𝐨𝐫𝐦.𝐭𝐟𝐬𝐭𝐚𝐭𝐞 𝐟𝐢𝐥𝐞 which keeps the all the run history showing the changes made to Infrastructure or what modifications are made in these run.










Comments

Popular posts from this blog

Top 10 high-level EC2 scenario-based questions to challenge your AWS & DevOps skills

 Here are 10 high-level EC2 scenario-based questions to challenge your AWS & DevOps skills 1. Your EC2 instance is running but you can’t connect via SSH. What troubleshooting steps will you take?  Check Security Group inbound rules (port 22 open to your IP).  Verify Network ACLs (NACLs not blocking inbound/outbound).  Confirm instance’s Public IP / Elastic IP.  Validate Key Pair and correct permissions on .pem.  Ensure SSM Agent is installed (Session Manager can help).  Check system logs on the console for OS-level issues. 2. You terminated an EC2 instance by mistake. How can you prevent this in the future? Enable Termination Protection in EC2 settings. Use IAM permissions to restrict TerminateInstances. Tag critical instances and set resource policies. 3. Your EC2 instance needs to access an S3 bucket securely. What’s the best way to configure this? Best practice: Attach an IAM Role with least privilege policy to the EC2 instance. Avoid hardcoding...

GitOps-Driven Management of VKS Clusters: Enabling GitOps on VCF 9.0 (Part 03)

  GitOps-Driven Management of VKS Clusters: Enabling GitOps on VCF 9.0 (Part 03) In the Part-02 blog, we walked through the process of deploying an Argo CD instance within a vSphere Namespace on  VMware Cloud Foundation (VCF) 9.0 , enabling a GitOps-based approach to manage Kubernetes workloads in a vSphere environment. With Argo CD successfully installed, we now have a powerful toolset to drive declarative infrastructure and application delivery. In this blog post, we’ll take the next step by demonstrating how to  provision and manage VKS clusters  directly through the Argo CD  UI and CLI . This allows us to fully operationalise GitOps within the private cloud, delivering consistency, scalability, and automation across the Kubernetes lifecycle. Importance of Managing the Kubernetes Cluster with a Gitops Approach Adopting a GitOps-based approach for managing Kubernetes clusters enables declarative, version-controlled, and automated operations by leveraging Git a...
 https://knowledge.broadcom.com/external/article?articleNumber=389217 VMware Aria Suite Backup and Restore Documentation Issue/Introduction This article host backup and restore documentation for VMware Aria Suite 2019 product lines. Environment VMware Aria Suite 8.x VMware Aria Automation 8.x VMware Aria Automation Orchestrator 8.x Cause Technical documentation has been migrated from docs dot vmware dot com to  https://techdocs.broadcom.com . During this migration, some content considered End of Life (EOL) or End of General Support (EOGS) was not targeted for migration. Resolution PDF files are provided in this article while these documents are restored to https://techdocs.broadcom.com. Attachments Backup & Restore with EMC Avamar for VMware Aria Suite.pdf get_app Backup & Restore with Netbackup for VMware Aria Suite.pdf get_app VMware Aria Suite Backup and Restore by Using vSphere Data Protection.pdf get_app