HashiCorp Terraform Reviews

I use the latest version. 

The solution allows us to work faster with ease and to set up new environments and workspaces. 

I would like to see a short-term option for a short-term plan. The last few versions contain plans with very long output which have since been altered. When one receives a plan involving many changes, it will not be applied. Even should nothing need apply, there is a very long history which is not really useful, as many find its application confusing. 

I have been using HashiCorp Terraform for around five years. 

The solution is pretty stable. I have no issues in this regard. 

The solution is pretty scalable. 

As the solution is open source, support is community based. 

There is a need for configuration management, for setting up the infrastructure from scratch. 

The set up process is pretty straightforward. 

The duration of the deployment varies with the project. Our company is involved in many projects. 

There are between one and five people who are responsible for maintaining the solution. 

I went with HashiCorp Terraform over that of CloudFormation, as the latter is complicated and hard to understand. HashiCorp Terraform was easier to learn across platforms, regions and multi-clouds. 

I use the latest version. It is important to try to not repeat oneself and to utilize the module provided by HashiCorp and others for training purposes. 

We use HashiCorp Terraform orchestration tool for infra provisioning (mostly servers), both in the cloud and on-premise environments. This allows for VM provisioning, networking, and storage management, especially in a cloud environment where we have many servers that can't be provisioned one by one.

The most valuable feature is the ease of infrastructure provisioning in a very large environment in the shortest time.

I initially found the initial HashiCorp Terraform difficult to comprehend. It's not straightforward especially in complex cloud environments, requiring proper training to grasp it. Even someone with a background in networking or cybersecurity would need guidance from someone knowledgeable.

Inclusion of revert function or rollback action for any invalid or wrong changes to resources.

I have been using HashiCorp Terraform for approximately one year.

HashiCorp Terraform is highly stable.

I did not use the technical support from the vendor.

Neutral

The initial setup of HashiCorp Terraform is easy to do. The implementation took a few hours to complete for a small cloud environment.

Terraform Enterprise plan is quite expensive!

HashiCorp Terraform is the best platform for creating and managing resources on cloud platforms and other services through their application programming interfaces (APIs) in a cloud environment.

I rate HashiCorp Terraform an eight out of ten.

We use this solution for infrastructure and support for a mobile application for a bank.

This solution could be improved by adding features such as CDM to accelerate the access of data by the users.

It would be useful to be able to test functionality when building infrastructure. Currently we use other tools to do this. 

We have used this solution for one year.

This is a stable solution. 

This is a scalable solution. 

The initial setup is straightforward. It took a few weeks to implement with the help of three engineers. 

This solution is a fast and secure way to provision infrastructure. 

I would rate it a ten out of ten. 

We are using Terraform to manage our multi-cloud requirement for different demos and test environments. It helps us set up the entire environment in a few mins with the exact configuration in AWS, Azure, or GCP, along with other setups like a database, Kubernetes, etc.

Terraform helped us to standardized our infrastructure setup and to reduce errors occurring due to manual execution. It has made our environment more efficient.

The most valuable feature is the support for different platforms like cloud, datacenters, VCS, databases, various storage types, and Kubernetes.

They have added a feature that helps us to import existing resources to our workspace, but if they can help us to create the code for the import, as well, then it would be a great addition.

We have been using HashiCorp Terraform for more than two years.

We should always check the changes or impact of new release which is common for all tools so for me its good in terms of stability.

The scalability is good.

We have used platform CLIs and other customized scripting solutions that need lots of maintenance and care.

The initial setup is quite easy and straightforward.

The setup for Terraform is quite easy and currently, we are using their community version along with Jenkins.

We have evaluated other options like CloudFormation and Cloud Deployment Manager, but those were platform-dependent tools, so not suited for our multi-cloud model.

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.

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.