HashiCorp Terraform Reviews

My company uses HashiCorp Terraform for cloud infrastructure provisioning. HashiCorp Terraform is the only IaC tool we use in our company.

The most valuable features of the solution are its simplicity of HCL language, its compatibility with multiple cloud providers, and its modules like the open source modules available, especially considering the fact that I work mainly on AWS. I believe that HashiCorp Terraform is one of the best products available in the market for my company's use cases. HashiCorp Terraform is also a feasible solution in terms of its availability of cloud resources.

I know a UI tool is available in the licensed version of HashiCorp Terraform. From a user's perspective, it would be great if a UI tool is made available in the open source version as well, but I don't think it may be introduced because of the high costs for it announced by HashiCorp in its licensed version.

HashiCorp Terraform can improve backward compatibility. From users' perspective, migration from one version to another is okay. The migration from an older version to a newer version is a big challenge in HashiCorp Terraform. We tried to fix the migration issues multiple times at our end and saw that some will not be compatible sometimes while, at times, certain aspects will be compatible with the new version.

I have been using HashiCorp Terraform for four years. I use HashiCorp Terraform v0.12 or v0.13. I use the open-source version of the tool for my company's internal usage.

Stability-wise, I rate the solution a nine out of ten.

Scalability-wise, I rate the solution a nine out of ten.

My organization has around 30 to 40 users of the solution.

The simplicity or complexity of the initial setup depends on the number of accounts involved in the setup phase on the cloud, along with the resources to be managed. Based on my experience, one won't find HashiCorp Terraform's setup difficult if the configuration and management are in place.

The solution is deployed on the public cloud. I know people who use the solution on private and hybrid clouds.

For those users with their infrastructure on the cloud, I would say that Terraform is a tool they can use immediately, even though other tools like Ansible are in the market. At some point, one may feel that Ansible lacks efficiency in a cloud infrastructure, which is a difficulty one may face when using Terraform in a bigger infrastructure. I would say that the combination of Ansible and Terraform is the best.

When following complex methods, Ansible is the best option. If you do too much configuration on the standalone file, then if not today, then tomorrow you might be stranded in a situation where you might not be able to edit or modify the configuration, especially when some improvements related to certain features have to be included in the product or your product's existing portal. It will be very tough to deal with, especially when it will be a single file with thousands of clients, making it a tough job to search. So you need to make sure that code reusability is properly using in your terraform code base.

I rate HashiCorp Terraform a nine out of ten.

We use HashiCorp Terraform for Infrastructure as Code (IaC).

The most valuable feature of HashiCorp Terraform is the custom modules. The custom modules are built for each piece, like network and security, based on how the customers are. Then, we can tie them together, centralize them easily, and build them.

HashiCorp Terraform state management could be improved to be used efficiently with multi-users. Even though there are logs, there are always issues I've seen with people manipulating the TerraForm state. We cannot work efficiently with the solution if the state is incorrect. Due to certain reasons, if I have to change some piece of some resource, I cannot change it. I have to destroy the whole thing and then build a new one.

I have been using HashiCorp Terraform for three years.

HashiCorp Terraform is a stable solution. I rate HashiCorp Terraform an eight or nine out of ten for stability.

Around 20 users are using HashiCorp Terraform in our organization.

I rate HashiCorp Terraform an eight or nine out of ten for scalability.

HashiCorp Terraform's initial setup is simple. Especially with TerraForm Cloud, you don't have to do anything since it's a SaaS platform. Also, TerraForm Enterprise is easy to install.

HashiCorp Terraform's deployment is very easy and doesn't take much time.

We have seen a return on investment with HashiCorp Terraform.

HashiCorp Terraform's pricing depends on the way people use it. Not everyone uses the solution the way HashiCorp recommends to use it. HashiCorp Terraform goes by workspaces, and workspaces are more expensive than nodes. The nodes are cheaper.

People implement the solution in different ways. So you can use the solution with less money and make it cheaper, but that's not the recommended way. If you use the solution according to the recommended way by HashiCorp, it is more expensive.

I am using the latest version of HashiCorp Terraform.

I recommend users build the framework and the modules correctly right from the beginning. Then, build the workspace as recommended by HashiCorp. According to HashiCorp's recommendation, one workspace should exist per application or environment. That's how people need to build it.

Then, modularize everything and make custom modules for the organizations. Especially things that stay out of the application, like security, network, and compute, should be in separate modules. Later, they can be brought into the application.

Overall, I rate HashiCorp Terraform an eight out of ten.

Our company uses the solution to deploy resources and infrastructure in Azure Cloud via the Azure DevOps pipelines. 

We have two developers who use the solution. 

It is easy to recreate an exact duplicate or output of an environment. 

The solution is much faster than manual deployments. 

It is much easier to create code than with ARM templates. 

The solution is quite easy to learn and use. 

It should be easy to automatically import everything at once from a manual environment or by a specific resource group. Currently, imports are only per resource so some automation is needed. 

The setup could be a bit easier. 

I have been using the solution for four years. 

From time to time there are stability issues with other providers and original providers in the solution. Stability is rated a seven out of ten. 

The solution is scalable so scalability is rated a seven out of ten. 

I have not contacted technical support. 

The setup for one laptop is quite easy technically.

If you are sharing the environment among staff, then the setup is a bit more complicated. You need knowledge to setup under this specific condition. Once you study it, you will be able to implement correctly. 

The setup is rated a five out of ten. 

We implemented the solution in-house. If you know how to do it, implementation is not too complicated and takes a few hours. 

We use the solution's free version. 

The solution is good for automation and better than regular ARM templates from Microsoft. It might not be as good as Bicep, but is better than most other providers. 

The solution is a strong technically and great for multi-provider or multi-cloud environments.  It is rated a top tool in the market. 

The solution is great technically for the cloud and automations. It can be used with Azure, AWS, Google, and other clouds if you know the syntax.  There are many resources provided and the free version works great for multi-cloud automations. 

I rate the solution an eight out of ten. 

HashiCorp Terraform is a tool used for provisioning cloud infrastructure. It is used in this specific use case to deploy and provision all services, including Kafka, MongoDB, and Postgres clusters, using infrastructure as code.

HashiCorp Terraform has greatly assisted in deploying a new service by automating the configuration of pub/subs and secrets on GCS and Drone. We are able to make changes and keep track of configurations by writing code and scripting through Terraform, rather than manually doing it on the cloud. This has led to a change in our perspective on deployment and DevOps.

The feature "Terraform Plan" is the most valuable in HashiCorp Terraform as it allows us to see the differences between the current infrastructure and the one we are about to deploy, keeping things safe. Additionally, we appreciate the use of the modules as it helps in making the application scalable.

The price of the solution could improve.

I have been using HashiCorp Terraform for approximately six months.

I rate the stability of HashiCorp Terraform a ten out of ten.

We have approximately 1,500 users using this solution in my company. We plan to increase our usage.

I rate the scalability of HashiCorp Terraform a ten out of ten.

I have not contacted support.

I have not used similar solutions to HashiCorp Terraform before.

I have seen a return on investment using the solution.

I rate the price of HashiCorp Terraform a seven out of ten.

My advice to others is to treat Terraform as code, not just another configuration management tool. It's similar to writing backend code, so approach it with the same mindset and level of care.

I rate HashiCorp Terraform a nine out of ten.

We use HashiCorp Terraform for Infrastructure as Code. It automates the deployment of infrastructure within the Azure platform. Terraform can manage almost all aspects of infrastructure provisioning. If there are tasks that Terraform cannot perform directly, you can use the Azure CLI or other tools and call them from within Terraform scripts.

Terraform has extensive integrations across various platforms. It includes modules that enhance functionality and support for secure practices, such as Terraform Sentinel, which offers code analysis capabilities. Security logging and backend security are crucial, particularly regarding protecting sensitive information stored in the backend. Ensuring private endpoint usage is pivotal to safeguarding against potential vulnerabilities.

Terraform's strength lies in its modularity and the ability to use variables. You can organize your code within local and remote repositories, making it highly modular. This modularity allows you to call specific components as needed. Additionally, Terraform can toggle certain functionalities on or off through feature flags, a unique and powerful feature.

Terraform should monitor the backend storage more closely. You can handle it within Azure, but HashiCorp should release a dedicated tool to protect those secrets and ensure they're fully encrypted but this functionality is on its way for Terraform. They do have functionality that encrypts secrets and rotates which is great just like what Microsoft have and should be used in the wider community to safeguard public cloud systems

I have been using HashiCorp Terraform for five years.

The product is quite stable. You may not notice the updates, but you do see frequent changes in revisions because they've stabilized the platform. They've also introduced significant new versions and providers that work hand in hand with it. I don't encounter many errors that I can't fix straightforwardly. As an engineer, you receive error messages if you misconfigure things, and it informs you about that.

I rate the solution’s stability an eight out of ten.

The solution can scale to any size. It is suitable for SMEs.

I rate the solution’s scalability an eight out of ten.

Arm templates where difficult to managed initially and took a while to manage in nested calls and nested templates

The integration is straightforward. Simply download the binary, test it accordingly, and authenticate via Azure CLI. I've used the standard binary because it's free and widely adopted for technical infrastructure as code.

The initial setup is very straightforward. I set up a Python environment, brought in Terraform, and utilized it with YAML. Everything has to be securely done. You have to set up some pieces on the backend. It's straightforward to deploy: get the binary, set it up on the build agent, and configure the settings the way you need.

Inhouse Initially but I have learnt form other teams and vendors as all teams structure their code differently with best practices

We are using the free version of the solution.

Arm Templates and PowerShell Azure initially Pulumi (early days)

I've been working with HashiCorp Terraform recently and have deployed environments with it.OpenAI has released GPT Terraform, which Microsoft is heavily investing in. Generic modules are available for deployment. Azure AI Portal and AI Studio are useful tools for creating models. It's straightforward to perform service training and update models for input-output data.

HashiCorp Terraform has made handling modules and variables more secure. They've integrated key vaults to ensure secrets and backend storage are protected. Accessing the backend storage could potentially leak sensitive information if not properly encrypted.

I'm using GitHub Actions and Azure DevOps. Additionally, I'm exploring an older system within the team that will be set up to support.

If the setup is built on old infrastructure, the backend of Terraform works and stores. Vagrant works differently where it doesn't need to check with the infrastructure to see what's there or updated. You get an API call for deployment.

Overall, I rate the solution as eight out of ten.

I am using the solution on AWS to scale our operations using Infrastructure as Code.

Terraform is the most useful product for creating Infrastructure as Code. It has a lot of consistency, and we can control it in code. It provides a self-service infrastructure.

The solution helps us save a lot of costs. The product’s integrations help us a lot.

The product must improve DevOps features.

I have been using the solution for about two years.

I never had any stability issues. I rate the stability a ten out of ten.

It is easy to scale the product. I rate the scalability a ten out of ten.

We use other solutions for security in DevOps.

The solution is deployed on the cloud. It is easy to deploy the solution. The documentation helps us a lot.

The tool has a lot of value. It pays for itself. We save a lot of time using the automation.

The solution is fairly priced.

We're still learning how to use DevOps with our SOC. We need to improve our use cases. The tool is helpful for us to keep the same standards throughout the cloud. Currently, I'm only using AWS. I'm planning to use Azure in a few months. I would advise people to start using the solution. It is a cheap tool and saves us a lot of work. Overall, I rate the product a ten out of ten.

We use the solution for three things. Firstly, to automate the infrastructure, like enabling Logpush to Datadog. Secondly, for Cloudflare AWS and Insight AWS. Thirdly, we use Terraform to create infrastructure.

It is one of the best things because now we have everything automated with Terraform. We didn't have an outage for the last three years because everything is written in a code, and every change we have made is recorded. If we didn't have a tool like Terraform, it would be extremely complex to achieve this level of maturity with infrastructure.

The state file is the most valuable feature because it helps one know what exactly one has.

The solution is complex when we use it for a loop. This is a problem, not because of the language itself, but because of how the infrastructure generally works. It's different from Python.

I have been using the solution for three and a half years.

It is a stable solution. I rate it nine out of ten.

The solution is not very scalable. I rate it six out of ten.

The initial setup is complex.

We have seen ROI with the tool's use. 

I plan to use the solution more in the future. I recommend people to use it as it is the best tool in the market at the moment to create infrastructure anywhere.

I rate it ten out of ten.

We use the solution for provisioning.

The most valuable feature is the solution does not need installation.

The solution is missing a lot of properties for specific resources.

I have been using the solution for almost three years.

The solution is very stable.

We just need to download the installer from HashiCorp. We don't need to install the solution; we just need to place the file on our system, point it to the enrollment variables, and then we can run Terraform. There are three or four commands that must be executed before we can start using the solution.

The solution is open-source.

I give the solution eight out of ten.

The solution is the most popular for provision in the cloud, not only in Azure.