HashiCorp Terraform Reviews

Our primary use for the solution is to create infrastructure on the cloud. 

We are a cloud integrator. We write our codes in Terraform and reuse them for multiple customers by changing the values. 

The most valuable feature is the great community support. 

The product can be improved by implementing a native provider service. With Terraform, you need to switch the provider's version and get functionality from only that version. 

The competitor tools have native providers. You don't have to wait and request the provider to gain functionality; it's provided directly from the cloud. 

The integration with this solution needs to be improved. For example, if you want to deploy something from Terraform to Kubernetes and make changes very often, practically, it isn't easy to implement. If someone deletes something accidentally, the integration won't function well.  

I have been using this solution for more than five years. 

I would rate stability a nine out of ten. I don't have any problems with the stability. 

I would rate scalability a seven out of ten. It is problematic when multiple people want to work on the same Terraform code.

This solution is best suited for enterprise-level companies, but medium and small businesses can also use it. 

The initial setup is straightforward. The deployment time for the solution is about thirty minutes. 

We are using all the deployment models for this solution. But I prefer to use the CI/CD pipeline, which involves running the Terraform code as a final solution. I also prefer the CLI platform on my computer for development. When I develop the code, I prefer running it from my computer. After the code development, I prefer to have its own CI/CD pipeline. 

I would rate pricing a ten out of ten. You can do everything with the free license of this solution. The paid license is not required to use Terraform. 

We used Pulumi for a project. We found that Terraform is easier to write code and works faster. 

But it would be best if you learned Terraform HCL language. In the competitor solution Pulumi, languages like Go, Python, and other languages can be used. There is no need to learn a new language to use Pulumi. 

For me, it's more complicated to write the same infrastructure. If you are a cloud administrator, you should use Terraform. But if you are a developer or want to deploy simple infrastructure with knowledge of the cloud, then you should use Pulumi.

I will rate the solution a five out of ten. This is because multiple other solutions get used with Terraform. For servers, we use Ansible, whereas, for cloud infrastructure, we use Terraform. Developers need Pulumi for implementation. Terraform is facing a lot of competition. 

I would recommend Terraform to others. If you have more than one environment, you will definitely need Terraform. 

It is easy to architect cloud infrastructure using the solution. Also, its simple interface helps in developing specific scripts.

They should provide more tutorials to understand the solution's use cases. Also, they include more specific features into it.

I have been using the solution for three years.

It is a stable solution.

It is a scalable solution.

The solution's initial setup process is straightforward. It takes a couple of weeks to complete. Once you define everything, you can start working on it right away. The deployment happens almost immediately.

I recommend the solution to others. I rate it ten out of ten.

The office was working out of their office and they had around nine clients. The workspace would be in AWS and doing a VPC manually would have been a really hard job. The time estimated for doing nine virtual private clouds would have taken more than a month or two. Using Terraform, they were able to finish it in two weeks. The speed at which we could create the infrastructure was much faster than physically doing it. Also, having an audit and log for all the infrastructure was managed a lot easier using Terraform rather than doing it manually.

One of the most valuable features is that it offers the ability to create a VPC, Virtual Private Cloud and VPN connectivity to the VPC can be automated without having to do it manually. 

I still struggle a bit when configuring VPNs when we have multiple rules. If we have five or six virtual private clouds and we have to give rights between those multiple VPCs, we can have big problems.  I think it was a learning curve and then we improved it. 

I have not come across anything that really stopped us from not doing anything for our requirement as of now.

I liked it because since it's scriptable, the way you create the infrastructure is the same way you can delete the infrastructure also. If you created 10 to 20 different services and objects in AWS using a Terraform script, it's much easier for a person to get the whole infrastructure down. You can do a backup and then you don't really need AWS services because either the client does not exist anymore, or there is some gap before the client comes back, you don't have to manually go and delete all the resources. One script would actually remove everything from AWS. 

Cost-wise, going through the script and then removing everything that you have created through the script is much better than manually doing it. That was helpful for the client as well.

We use it to manage infrastructure. For day-to-day work, the main developers were not using Terraform, so it was only three of us who used it. We were working on Terraform, created those scripts, and then gave it to the client for whom I was doing the work. Since it's now scriptable, they are able to manage and do all these small changes. They don't come back to me. Since they don't come back to me, it seems like it is working fine.

Terraform keeps updating its scriptable platform, the engine through which they communicate. So if there is any change in AWS, they keep updating it. Even from the deployment side, they have to be aware of the features, which Terraform still supports and the features, which Terraform doesn't support and then work around accordingly.

The initial setup, like doing the AWS credentials, putting it in place, and getting the API keys are the parts that took time. Otherwise, it is a lot faster and the learning curve is also much easier since it's a YAML-based scripting language. Even a non-programmer in a normal office can understand what is happening in the flow.

The deployment took around 15 days. In around 20 days we were ready with the Terraform scripts and then made small changes. Every time they need a new infrastructure that requires a small change, it would take a day or two. We created the initial Terraform script and gave it to a client so that it could later be managed by the client itself to create and run. Fifteen days was good enough for us to create and test the Terraform infrastructure and then give it to the client.

We started the deployment by seeing how we would divide the infrastructure. One is the list of infrastructure, which we would need irrespective of the clients for the VPC, VPN gateway, and active directory services. Those are all mandatory items that we would need for all the VPCs. And there are some items that are client-specific. We divided it into multiple parts. One is generic, which you will need for all the clients that are a base level. Then you keep playing the client's specific scripts on top of the base script.

It's open-source.

Rather than doing a monolithic Terraform for the whole infrastructure, it would be good for the script to be reusable. Use the base level script that every infrastructure would need. Generating a local IP network and then creating two instances or creating some databases and other basic scripts that all the infrastructure would need should be a base level script. Then add on your base level script with the add-on scripts on top of the base script to create infrastructure that is specific to clients. You can reuse the script, the same base group for many other purposes as well.

Before using Terraform, for auditing, creating machines, etc, we would either rely on AWS infrastructure itself or documents that had infrastructure-related data. Using Terraform, a lot of this data was captured automatically since it's a YAML script. It could be easily exported as a document or Excel file as well. Documentation and infrastructure was much easier to maintain than doing it otherwise.

I would rate Terraform an eight out of ten. 

We are using HashiCorp Terraform to deploy infrastructure for our customers in Amazon AWS.

Our process has been made more efficient with the use of HashiCorp Terraform. This includes the ability to create deployments while also avoiding errors and misconfigurations. With this solution, we can ensure consistency in the deployment of all our customers.

The state file is the most beneficial aspect of HashiCorp Terraform. It enables the retrieval and utilization of a previous state to build upon. This feature is particularly important since it allows for the identification of changes from the previous state, making the state file a critical component of the process.

When a misconfiguration or drift occurs, fixing the issue can be difficult. For instance, if there is a change in API calls while a script is running, it can be challenging to make corrections. This may require additional review and modifications to the code. I recall an instance where an industry budget creation process was altered, and it took significant time to amend the code. In fact, I had to add five or six different script portions to resolve the issue.

In a future update, it would be beneficial for HashiCorp Terraform to include a code-writing feature. There is the availability of third-party solutions, it would be preferable to have the ability to write code, create a plan, and receive feedback on what will be implemented. It would be great if the generated code was easily readable and viewable, as this would be an exciting addition.

I have been using HashiCorp Terraform for approximately two years.

My advice to others is its crucial to handle key and access management properly because the most convenient method is to add your key to your computer's environment variables. However, this approach is not the most secure way to manage your keys. Therefore, exercise caution in this regard.

I rate HashiCorp Terraform a nine out of ten.

We use this solution to manage our resources in a fully automatic way. I'm a senior Azure DevOps engineer and we are users of Terraform. 

I like the Centrix feature which gives us the ability to create loops. I also like that modules can be reused extremely easily. This is a super robust solution and I would recommend it to anyone. It has a great user interface and integrates well.

It would be helpful for us if the open source tech support was a little better. 

I've been using this solution for four years. 

The solution is stable.

The solution is highly scalable.

We use the free open-source version of Terraform so it can take time to resolve problems. The issues are generally minor, so it's not a big deal. 

Neutral

The deployment can take anywhere from 10 minutes to two hours. 

I rate this solution ten out of ten. 

HashiCorp Terraform is a binary executable file, that you can download to your PC and manage any cloud solution in the world, such as Google Cloud Platform, Amazon AWS, OpenStack, CloudStack, or VMware. When you use DevOps in your company, it's a useful tool for it.

The most valuable features of HashiCorp Terraform are automation and management capabilities.

HashiCorp Terraform could improve the integration with the VCloud Director. When we manage the VCloud Director we end up wasting our time when creating virtual machines. HashiCorp Terraform knows about these issues and I think there might be a workaround but they should incorporate the fix in an upcoming release.

I have been using HashiCorp Terraform for approximately one year.

HashiCorp Terraform is a stable solution. We did not have any problems.

The scalability of HashiCorp Terraform is good.

I have not used the technical support from HashiCorp Terraform.

HashiCorp Terraform tool is pre-installed on our DevOps engineer's laptops, and in our GitLab Servers. We assign it to a selection of virtual machines. We just run it, and then we perform some functions, such as creating systems or modifying CPUs or RAM.

We did the implementation of HashiCorp Terraform in-house. We have a good team of three programmers and DevOps engineers with experience.

We used one engineer for the implementation of HashiCorp Terraform. 

HashiCorp Terraform is a free solution.

I rate HashiCorp Terraform a nine out of ten.

We are using it for infrastructure as code automation. We are running its latest version.

The state backend, automated describe functionality, modular structures, and variablization using templates are most valuable.

The state locking functionality can be improved. In certain situations, we have to force-unlock the state, which sometimes does not work. When that happens, we have to manually go to the state backend and remove that particular state, which is kind of a cumbersome process.

It should also have more functions, more expressions, and support for more products.

I have been using this solution for almost four years.

It has good stability.

It is good in terms of scalability. We have almost 35 to 40 users. We definitely plan to increase its usage.

We did interact with their technical support. It was easy to schedule a call with them. It was also easy to contact their sales team and the support team. It was definitely a good experience.

We had AWS CloudFormation as well as Azure ARM templates.

Its initial setup is quite good and simple. It didn't take more than one and a half hours.

I did it myself. We have four people for its maintenance. We have one admin and three deployers.

They have given it to us at a monthly cost, but it is on a yearly basis.

I would advise others to understand the state backend and how Terraform works. They should also go through functions as well as expressions in the Terraform official documentation.

I would rate HashiCorp Terraform an eight out of ten.

I mainly use it for infrastructure automation. I use it to provision servers in different cloud providers and in-house with the principles to create a Kubernetes cluster. If you have a master node concept I would create the master and find related text.

The main function for me is to create infrastructure.

Because of Terraform, companies have a lot of options to ensure growing faster than what was normal in the past. Usually, it takes about two to three weeks to be done. But with Terraform, the approval is there and you can take it out in half an hour or ten minutes to deploy. That is a really good benefit of using Terraform.

I like the function that shows me a preview of what is happening in the infrastructure. We created it to find a workflow and find out which area has an issue over a certain period of time. If there is a patch with a change to the environment, I don't have to change a lot of code, I just have to change one or two variables with very few modifications to make sure the environment reflects that. So I love that.

I'm really happy with Terraform because it has really come a long way up to this point. It has a stable version.

For the moment, Terraform is actually working really well with a majority of our providers and technologies. At this point, the news cables are about 80% to 90% from the feed. I don't see a problem with the product. But if you're talking about homes, bugs and some certain features, I think there are features that could be included. For example, if you are copying something from a well running machine to a remote machine, there are some issues with the current version, but it is acceptable.

I have been using HashiCorp Terraform for three months.

HashiCorp Terraform is extremely stable. But there are bugs that we are finding when doing some things. It's a really good product.

For the moment I am the only one using it. But if you're talking about my clients and thinking about jobs and growth and the community behind it, it's really good.

What I did first was see how this works, ask the community, and check all sorts of blogs that are really helpful. There is a lot of talking about Terraform so it is easy to study. It's not that hard to get a grasp on it. The information is there to make sure that someone can get this technology into their hands. I think the initial set up is really good.

If your core group is ready, it takes 10 minutes to one hour to make the magic happen. Then you have to make sure you know what you want. Once you get the job details it can be used in different projects because in the end everything is the same. Start with the hardware. It's about individual talent mainly. For me it takes about four to seven days to create a functioning Terraform.

I did it in-house.

HashiCorp Terraform is a great product and I think anyone working with infrastructure should have it.

On a scale of one to ten I guess I would give HashiCorp Terraform a nine.