HashiCorp Terraform Reviews

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 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.

HashiCorp Terraform does a good job and helps us set up all operations.

There are no specific valuable features as the whole product is good.

Terraform doesn't support Artifactory as a backend.

We have used this solution for about four years and are using the latest version.

It is a stable solution.

I am unsure about the scalability.

We have never used their technical support.

We have not used any other solutions.

I rate the solution a ten out of ten. HashiCorp Terraform is a rapid and promising tool.

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 enables us to create our cloud implementations without a technician needing to sign on to the cloud.

We are able to do multiple hybrid cloud implementations for clients that need to support Azure and AWS. 

It allows for the abstraction of the work away from the developer into automated processes. 

The reuse simplification is very good. 

It can enforce DevOps. 

It is stable. 

Technical support has been fine. 

The workflow and automation could be better.

The user interface could be easier for non-technical people. 

There's a learning curve involved with the setup; however, it is low to medium. 

I've used the solution for a long time. I've used it for 12 years at least. 

The stability is excellent. There are no bugs or glitches. It doesn't crash or freeze. 

It's not a customer-facing solution. We've never had an issue with it. However, it is not a primary concern of ours in terms of the ability to expand. 

Most business analysts and sometimes architects use the solution. We have 1700 people in our organization, and we are doing 100 projects at a time. Almost all of the projects require the use of the product. Half of the people are engaged in the solution in one way or another. We have about 750 people using it. 

Technical support is very good. 

The initial setup is very simple for the most part. 

The pricing is expensive. It's more for enterprise implementations. The cost is above average in general. 

We're a consulting company. 

I'd advise other users to automate to the greatest extent possible to get the best ROI.

I'd rate the solution nine out of ten, even though the workflow is not the strongest on the market. 

HashiCorp Terraform is a system solution that allows for infrastructure to be managed as code. allows for the efficient creation and management of infrastructure by packaging everything together in one package. This includes the networking, security, and encryption for Google Kubernetes Engine (GKE) deployment.

By using HashiCorp Terraform, the infrastructure is all in one place and can be easily tested and checked for security vulnerabilities before deployment.

The valuable features of HashiCorp Terraform are the infrastructure can be written, shared, and collaborated on using code, which speeds up deployment. Additionally, bugs and issues can be fixed in the code and redeployed, making it less risky. It is a more efficient method compared to the traditional approach of writing scripts to set up infrastructure.

The infrastructure is transparent, as it is stored in a source control system, such as Bitbucket, making it easy for all team members to access and review. Furthermore, Terraform enables the creation of a deployment pipeline using tools, such as Atlantis, which automates the process of scanning and deploying the code. This streamlines the deployment process and adds features, such as auditing, risk management, and security scanning to the deployment process. Terraform provides a more organized and secure way of managing infrastructure, compared to the traditional ad-hoc method.

HashiCorp Terraform is an open-source tool that relies on external developers to create plugins to expand its capabilities. However, this approach can be problematic as not all plugins are created by professionals and some may have security vulnerabilities. In the case of GKE, Google has created a solid plugin, but for other services, one must search for plugins on the HashiCorp Terraform registry, which can be hit or miss, as many plugins are created by students or hobbyists, who may not continue to maintain or update them. This model of open-sourced plugins may not be the most reliable or secure way of expanding the tool's capabilities. 

It is possible that when using a plugin with HashiCorp Terraform, there may be security issues or the plugin may become outdated in the future. HashiCorp Terraform only takes responsibility for the infrastructure and code of the program itself, not the plugin. This is a point of concern as it is the responsibility of the user to police and manage the plugins, which can be a significant overhead. Additionally, the solution requires plugins for modules, so without them, Terraform cannot communicate with certain resources.

To improve this, it would be beneficial if HashiCorp Terraform had a system in place where they certify and test the plugins. This would take the burden off of users and reduce the cost of using the solution. The current system relies heavily on open-source plugins which may not be fully developed, lack features, or may not be secure. It is not uncommon for users to have to fork or manage these plugins themselves, which can be a significant undertaking.

The module system in the solution is not the best, as it forces users to rely on third-party developers who may not be qualified from a security or engineering standpoint. This can create a problem for users as they may not have access to all the features they need, and may have to fork or manage the plugins themselves. HashiCorp Terraform, as the creators of this system, should take more responsibility for the management and security of these third-party plugins.

The use of open-source code, such as that used in this solution, can present issues as it may not always be fully supported or maintained by its creators. This publicly traded, multi-billion dollar company, may not want to take full responsibility for the plugins and modules that are created by third parties. This can be problematic for users, as they may have to police the plugins themselves to ensure they are secure and functional. Furthermore, while some companies such as Google may have the resources to create their own Terraform plugin and take responsibility for it, many other companies and developers do not have the same resources and may not take responsibility for maintaining their own plugins. This can lead to a broken system where users may have to pay extra to have broken plugins fixed. Overall, this highlights the need for a better system of support and maintenance for open-source code and plugins.

I have been using HashiCorp Terraform for approximately four years.

The solution is scalable. It is well suited to managing complex cloud environments, such as Google Kubernetes Engine, that require various services and configurations.

HashiCorp Terraform is a cost-effective solution.

HashiCorp Terraform has issues with testing and the modules. Overall, the concept is great. What they did works well. However, the extension to it is not the greatest.

I rate HashiCorp Terraform a seven out of ten.

I use this solution for infrastructure for my projects that are deployed in Google Cloud. I work in EPA systems. 

The solution allows you to have infrastructure-like code which is basically what Terraform has been about. Terraform makes it easier to figure out the kind of problem that has occurred, why, and who was responsible.

Although using an older version, I've found the biggest advantage of Terraform is that it can be used across multiple cloud providers and multiple platforms and it has a simple API. 

The biggest disadvantage of Terraform is its lack of flexibility in common programming languages. It also lacks flexibility in creating some functions like complex expressions to declare random variables, and features that require any programming language. Those issues are because HashiCorp is trying to keep the API as simple as possible. I would like to see some idea of functional programming in Terraform. It would be great if you could process your data and push it back to the model. It would mean a huge improvement in flexibility. 

I've been using this solution for three years. 

The solution is stable and we haven't had any problems in that regard. 

The solution is scalable and we are constantly working on increasing of size of our infrastructure.

The initial setup is a little complex but not very difficult. Implementation time depends on the size of the deployment. Our deployment was carried out in-house. We need at least one person per 50 models of Terraform for implementation. 

We've had a return on our investment because it's decreased the overall ops overhead via the front team.

I am not using a payable Terraform although I'm quite familiar with the price and don't consider it to be expensive. Licensing costs are mid-range. 

I would suggest reading documentation and experimenting with the solution. 

I rate the solution 10 out of 10. 

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.