Terraform MCP Server

What do you like best about the product?

What i like best about Terraform is its ability to define and manage infrastructure as code in a consistent and predictable way. It makes it easy to version-control infrastructure changes, review them through code, and apply them across different envirinments. I especially value the reproducibility and the ability to automate provisioning across cloud services, which significantly reduces manual configuration and potential human errors

What do you dislike about the product?

What i dislike about IBM Terraform is that the learning curve can be quite steep, especially for beginners, and debugging configuration or state-related issues can sometimes be complex. It also requires careful state management, which can add overhead in larger environments

What problems is the product solving and how is that benefiting you?

We struggled with manually provisioning and managing cloud infrastructure across environments, which often led to inconsistencies and configuration drift. With Terraform, we can define infrastructure as code and automate provisioning in a consistent and repeatable way. This has improved deployment speed, reduced manual errors, and made infrastructure changes more predictable and easier to track through version control

What do you like best about the product?

I use it to automate the deployment and management of the servers and databases that make up the back end of our enterprise data systems, such as our new Human Resource Management System and a facial recognition based attendance system. We use it to create and maintain the server and database clusters across our cloud providers to ensure our development, staging and production environments are identical.The level of automation and repeatability that it offers is great. We were doing all of the server provisioning, network rule creation, and database cluster creation for our Python stacks by hand and this was a painful work of clicks. Now, it's all written down.My favorite feature is the plan and apply. Having a simulation that tells me what will be created, changed, or deleted before anything actually happens gives me confidence, especially when we are changing the critical systems for our HRMS. And there's a huge provider ecosystem. Whether we're making changes to cloud networks, creating load balancers, or managing DNS, there's probably a provider for that. And it's provider-independent, so we aren't tied to a single provider's set of tools.

What do you dislike about the product?

Probably the most painful thing is dealing with the state file. If you're not set up right with remote state and state locking, things get complicated. We've spent some time scratching our heads because of state conflicts when more than one person has tried to push.And while the HashiCorp Configuration Language (HCL) isn't the most challenging to learn, it certainly takes time to get used to. Your junior team members have to come to terms with advanced state modules, for_each and dynamic blocks. Lastly, importing existing infrastructure, that you create manually, into the state file using the import command is still not a very efficient process.

What problems is the product solving and how is that benefiting you?

We had a lot of problems in the past where our staging environment for the attendance system was slightly different to production, and we got funky bugs sometimes. All that went away with Terraform; we simply use the same module and pass in different variables to create both environments.It took days to set up new infrastructure for HRMS modules before, with tons of manual work and ticket exchange. Now we just edit our templates, commit to a branch and our infrastructure is available in a few minutes from our CI/CD pipeline.It's comforting to know that the entire infrastructure is in version-controlled code. In the event of a catastrophic failure in a region, we can easily redeploy the entire stack in another region.

What do you like best about the product?

Terraform allows us to manage infrastructure centrally if we have are on hybrid clouds platforms I like it's support to multiple platforms centrally

What do you dislike about the product?

Some times due to changes made manually causes drift issues and creates state file goes out of sync

What problems is the product solving and how is that benefiting you?

It allows us manage infrastructure and applications very efficiently

What do you like best about the product?

It integrates smoothly with our CI/CD pipelines. We can also reuse modules and solution templates, which makes setup and delivery much easier. It offers strong security and compliance features, and it works well across multi-cloud infrastructure.

What do you dislike about the product?

Overall, the product looks good. Need to improve the state file concepts.

What problems is the product solving and how is that benefiting you?

It enables faster infrastructure delivery and works smoothly across multi-cloud environments. I also like that it includes version control and a complete audit trail, plus reusable modules that make it easier to standardize and repeat deployments.

What do you like best about the product?

The best thing that comes to Infra teams' hands to organise the chaos of resources provisioning and managing, I can't imagine my life without TF.

What do you dislike about the product?

Moving away from the open-source community.

What problems is the product solving and how is that benefiting you?

NO ClickOPS anymore, which is helping in organising our infrastructure management across all platforms.