HashiCorp Terraform Reviews

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 have about 50 users.

With Terraform, you don't need to understand the console of your cloud providers. You only need to understand how Terraform works, and you manage your infrastructure tools in Terraform.

In Terraform, there's a file called main.tf, where everything starts. In the main.tf, you need to specify the provider you're using. For example, maybe you want to use GCP, but you don't want to work on GCP. That's where you will list everything you need. It's like a key for you to access GCP. 

Sometimes, it can be challenging to undo. Let's say I'm using the provider here, and you want to use it on your site over there. You have to delete the provider you are using before switching providers. It doesn't sync well. The providers don't sync well. And also the documentation sometimes, they need to work on the documentation of Terraform. They're not concise.

The error logging could be better. Sometimes, when you try to set something on Terraform, it gives you an error, but you don't understand how the error has been logged. 

I started using Terraform two years ago.

Terraform is one of the most stable products HashiCorp provides

Terraform is scalable.

Terraform is an open-source product, so we rely on documentation. I rate the Terraform documentation five out of 10. It should provide more examples about the way you should write some resources or models.

Setting up Terraform is straightforward. You only need to deploy the binary. I rate it 10 out of 10 for ease of setup. 

I rate Terraform seven out of 10. There aren't many products that do what Terraform does. It's easy to use and set up.

We use HashiCorp Terraform to deploy applications and infrastructures.

The most valuable aspect of this solution is the coding of our infrastructure. You can code it once and run it multiple times.

It works great for us.

We have had no issues integrating with other products.

It does everything we need it to do.

There is always room for improvement somewhere. I don't know everything about the product.

I read about the improvements and the different things that are coming out all of the time. They continue to maintain it.

I have been working with HashiCorp Terraform for two years.

HashiCorp Terraform is very stable. Once you have coded it, it is good.

The HashiCorp Terraform solution is scalable.

I have not contacted technical support. I have not needed it.

The initial setup was straightforward.

It is very simple to maintain.

I am not aware of the cost, my customer deals with that.

I would suggest going for it. I have not had any issue with it yet.

I would rate HashiCorp Terraform a nine out of ten.

We use the product for cloud deployments, specifically provisioning services in the cloud.

The platform's most valuable feature is the infrastructure as code aspect, which allows us to code the infrastructure part, making deployments more efficient.

One area for improvement could be the inclusion of more dedicated Terraform providers developed by the companies themselves, rather than relying on third-party developers.

Additional features could include more intuitive environment-specific configurations and possibly enhanced support for development and production environments.

I have been using HashiCorp Terraform for approximately six months.

I rate the platform's stability a ten out of ten. 

I rate the platform scalability a ten out of ten. 

The initial setup was straightforward. I rate the process a ten out of ten. 

The product can be cost-effective, especially if you use the CLI and do not require the cloud solutions provided by HashiCorp. It can be used for free, which is beneficial for small companies.

I rate HashiCorp Terraform a ten out of ten. 

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. 

Terraform is the infrastructure as code solution used across our business. 

The way the modules are divided for infrastructure provisioning and are set up for reliability to offer plug and play functionality has been really useful. This solution makes it easier to manage a multi-cloud environment and have your entire infrastructure as code. 

On occasion, I have noticed a number of bugs in this solution that have needed to be fixed. 

In a future release, it would be great to have an easier way of troubleshooting. We'd like to have a dashboard where company management can get a full view of provisioning.

I have used this solution for three years. 

This is a scalable solution. 

It would be great to have faster resolution of instances where there are bugs in the system. 

Neutral

The initial setup is straightforward. 

I would rate this solution an eight 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.