Basically whenever your DevOps engineers are overseeing in excess of ten machines or when you need numerous groups not zeroed in on DevOps to assist with claiming the framework facilitating their code. Prominent sentiment is that Terraform isn't exceptionally secure, fight tried, and spilling mysteries happen effectively on mishap. Thus, Terraform is not so great when you need to store bunches of touchy mysteries that your organization is lawfully needed to watch in case it is the finish of you.

Deploy Infrastructure rapidly and dependably. Repeatability because of utilization of modules. the suppliers work really hard keeping awake to date on the most recent changes from the Cloud suppliers Features Updates. This makes exploiting the new elements dispatched not an issue. Terraform is totally and absolutely better than utilizing CloudFormation straightforwardly.

The actual language is somewhat surprising and this makes it difficult for new clients to get onboarded into the codebase. While it's improving with later deliveries, essential ideas like "map a variety of choices into a bunch of designs" or "apply this rationale in the event that a variable is indicated" are conceivable however superfluously unwieldy. A rollback component would be a welcome expansion to Terraform. At the time I'm composing this, when Terraform experiences a mistake, it stops on the progression where the blunder is experienced and any assets recently made are left set up. While this is wanted as a rule, and choice for moving back those assets would give usefulness like other IaC devices.

Using Terraform allows us to use the Infrastructure as Code pattern (IaC). This means, rather than logging into the cloud service providers and manually amending things and not being able to do all those things quickly, accurately, and repeatedly (for deployments), using Terraform allows us to do all of that automation.In addition, because the changes are done as code, they are submitted to a version control system (Git) and so reviewable, approvable (or not), merged, and automatically deployed by a secure pipeline setup.

The ease of use and the speed at which bug fixes and related enhancements can be submitted via GitHub and be approved and so you end up running your amendments without needing to work around them.

One aspect is that there is a library that doesn't include all aspects of Terraform and so dependent applications are not fully capable of exposing all the aspects.

1. There was generally one example on each resources in terraform documentation which makes understanding a bit challenging. 2. There are very few developers with the terraform experience. 3. After writing the terraform scripts, the developers has to check the terraform plan properly before proceed the terraform apply command . There is a possibility that Developers run terraform apply command directly which would lead to deletion or modification of the resources and once resource is modified or deleted, there is no way to get the resources back.

1. Terraform state file which keeps the record of all the provision resources done by using Terraform script. 2. Reduces the repetitive task of developers: If there are resources which are created in Development environment and we need the same resources in Production environment too. Then instead of developers provisioning resources manually, we can easily reuse the terraform scripts that were used in Development environment to provision resources . 3. Terraform manages infrastructure on multiple cloud platforms like Azure, AWS, etc.

1. Less Examples in documentation. 2. Less support. 3. Since Terraform is new IAAS, there are many changes or upgrades going on.

We manage a multicloud infrastructure using Terraform for a major corporation. Terraform has been very flexible, easy to plugin with other systems. Without Terraform, managing a multicloud environment(and even hybrid env where few resources are on-premises) would have been a lot harder.

1. It is very extensible and works with multiple cloud platforms, popular hosting platforms like DigitalOcean, GoDaddy etc. Terraform uses providers for interacting with vendor specific APIs for provisioning infrastructure. 2. It uses HCL (Hashicorp language) which is quite powerful compared to plain YAML or JSON. Many other IAC tools use plain YAML or JSON - which can be limiting. With HCL, you get for loops, conditionals, and even the ability to get data from different data sources and even shell scripts 3. It is easy to run Terraform code from a Jenkins or any other build pipeline.

The state file management could be better. Although wrapper solutions like Terragrunt exist, it would be great if Tearrform's native capabilities with state management could be even better. Other nitpick is: secrets end up in plain text in state file. Hashicorp suggest using their product vault to avoid this issue. But, not everyone uses or wants to use Vault.

my overall experience has been a great one so far.

What i like most is terraform is cloud agnostic and i like the reusability of terraform modules for faster infrastructure provisioning.

what i like least is that when we write thousands of lines of code then managing the state becomes difficult.

Overall, the experience is great. It allows us to support complex cloud infrastructures without the risks of manual work.

Terraform was the first big player in the infrastructure as code game and became a de-facto standard. Byupporting different providers, it allows integrating a huge variety of components and helps to avoid Cloud vendor lock-in.

Breaking changes across versions make supporting it a bit more complex than it could be.

Amazing software which really helped us to remove Human errors. We had created a Terraform meta repository which stored the state of whole GCP project and recreated any resources if not working properly/deleted. Helped a lot to manage huge infrastructures.

Terraform supports a lot of 3rd party tools. And there are modules from many Cloud providers. The thing I like is that many indie developers write useful modules for Terraform which really helps in automating important tasks. The sky is the limit in automation when you are using Terraform. For example, we used to use Venafi software for SSL renewal which was a manual process and the certificates were placed in buckets. But we were able to automate the process using Venafi provider and local-exec.

User and Access management is a miss. We had to use workspace, and shell scripts to check the correct access of different resources.Also it can get complicated if you don't have a structure for your code. So using templates from start is a good way.

I have worked with clients that have their deployments in a word doc with 50+ steps to follow. Most of the time the documentation is outdated. To follow a doc of 50+ manual steps you will spend a good 3 - 4 hours if uninterrupted. With terraform I can create infrastructures in minutes and the code is the instruction doc of how the systems are built. I can review a deployment's template and see little enhancements or requirements specific to the system. We don't have to give up quality either since human error is solved in code. Terraform allows me to scale up easily by adding variables like "count" to deploy a number of machines. The best part is that I can easily integrate it with Jenkins or Azure DevOps pipelines, Vaults for secret management, ansible, etc.

We work with multiple clients, one might have Google Cloud, the other Azure, another Oracle Cloud and some VMWare. Terraform makes it easy to deploy in the cloud or on prem. 80% of the time I am using modules that have been created by others which speeds up our deployments.

Learning curve for IT teams that are used to manual deployments.

With HashiCorp Terraform, multiple teams in our organization can make changes to our AWS cloud infrastructure concurrently, synchronizing via Git. All resources are visible in the Terraform code as modules, and the code is highly reusable: our Infrastructure team defines modules that the application teams can use and customize via configuration parameters. The terraform plan and apply steps ensure repeatable configuration of our cloud resources even if they need to be recreated from scratch.

For new users it’s quite hard to learn: the syntax is not very intuitive (even though it is human-readable) and many modules require positional arguments.

Best tool for manage infrastructure code ,version and reuse to multiple environment. It is very easy to learn, implement . It has great community to support and solve issues. Terraform supports multiple clouds and it is very easy to integrate. We can use automate template to build application faster.

Terraform is best cloud management tool which provide infrastructure as code service . we are using terraform for AWS infrastructure management as code. We can use multiple workspace for our project and destroy workspace after use. Terraform uses HashiCrop language for creating human readable infrastructure code we can reuse same code , maintain version and source control. Terraform registry provide ready to use quick feature for easy development .

The only cons I found that sometime it takes times.

So far nothing but praises. The team is all very impressed.

Makes most things easier. Learning HCL and transforming to Infrastructure-As-Code is is a paradigm shift and not an easy one but a very interesting one which will help us become more agile and deliver faster and more reliable.

A steep learning curve for many and it a very different way of thinking doing IAC but Terraform makes it easy to deliver the same product consistently.

Overall, terraform is superior to using cloudformation & even comes to help if you decide on switching from 1 cloud provider to other. Terraform also is very efficient & works seamlessly with Jenkins/circleCI for automation. Recommend using terragrunt as wrapper for terraform, it helps in configuring & running terraform scripts in a better way.

Foremost, terraform is cloud agnostic so you just select your cloud provider and get started with provisioning cloud environment with terraform. The language is easy to understand & allows you to create reusable templates & modules. When making changes it shows all the changes in state that are going to be made during terraform plan, which is very helpful before we actually start applying them. You can also use remote executors to run some external logic of code through bash before provisioning.

Looping strategies like for_each are rather complex to understand when you are new to terraform. It does not have a rollback feature & if something fails all the changes before that failed change would still be applied. Some conditional logics are unnecessarily cumbersome. Also overally analytics for users running plan & apply is missing, it's better for management purpose & debugging the plan which might have caused an infra issue.

We have migrated all our infrastructure, based on AWS and K8S, with an IaC approach thanks to Terraform. With Terragrunt we can now manage different environments without the need to duplicate code.

There are a lot of providers available for free. A provider allow you to configure services for a particular cloud provider or service. In the last versions they have improved a lot the process to calculate the differences between the status on the code and the status on the target infrastructure.

Terraform don't offer a ready to use and free system to manage different environments. You have to use branched or external tools like Terragrunt.

A must-have for defining infrastructure-as-code. HashiCorp enables multi-cloud, vendor agnostic IaC which increases the flexibility, reduces the risks inherent with vendor lock-in, and enables things like DR.

Open source versions allow you to get started straight away, with cloud and enterprise platforms that easily let you take it to the next level. These tools are a must have for any cloud computing shop. The ability to define the computing environment in code in a platform neutral way, provides the business with the flexibility necessary in 2020.

Some quirky things in the HCL language, but major improvements were made in HCL2 (speaking specifically of TerraForm). It does take some time to get going with some of the concepts, but the documentation has drastically improved.

HashiCorp's Terraform is the software to use if you are looking to be able to construct or reconstruct entire infrastructure of an organization/project in a very short period of time and maintain the changes as code.

● HashiCorp Terraform Integrates with over 125 providers including major cloud providers such as Google Cloud Platform, Azure, AWS etc, version control repository hosting providers such github, gitlab etc and many more. This makes provisioning, management, updating, maintenance and destruction of resources easier. ● HashiCorp products have proper and efficient documentation that makes a new user get started easily. ● HashiCorp products have a large and active community support since their products are open source. ● Hashicorp products have an easy to use interface.

● Management of state files that holds information of the infrastructure and changes may be an issue sometimes especially if a number of users are allowed to carry out new changes to the infrastructure.

Once you get the basic syntax and familiarize your self with the error messages, things become simplified. Overall (with few limitations) I am satisfied with this product.

Easy to use once you get the syntax Proper documentation available in the Hashicorp site Integration with Git works good State File changes are accurate Software is stable

Some of the error messages are very cryptic and difficult to debug With more and more IAC being deployed, the state file becomes bigger and bigger and the checks for changes become slower and slower. No UI component is there to resolve issues

Overall experience is very good. As a cloud Engineer, for me Terraform solves most of the problems working with multi-cloud.

The best thing about Terraform is it's a free, open-source, and very easy-to-learn tool for provisioning and managing infrastructure as code. Some features like version control, reusability of modules, and multi-cloud features are very well integrated.

State management can be a bit complex sometimes. While starting with Terraform, users need to learn a new language ie HCL.

Overall it has been great tool to setup infrastructure on hybrid cloud

Infrastructure as code implementation, cloud agnostic technology, configuration management, single source of truth for infrastructure setup

Constant upgrades needed to get new features, pre-defined directory structure, lots of missing features/bugs in the Azure provider

Good documentation and examples are available to get started. It supports deployments to multiple cloud providers.

There are a few aspects in deployments that the terraform doesn't support. for example in the case of AWS API gateway deployments, it doesn't really deploy your stage API gateways and you need to do it manually. This is just one example but as you dive deeper you will find many such smaller hurdles which can get frustrating to debug.

It had a very relevant and positive impact on infrastructure deployment.

Agnostic to cloud provider. Very well documented and supported by the community. Many available modules at Hashicorp. Certification availability.

Interaction with APIs can lead to timeouts which stops implementation. Even though it is a provider responsibility, it could be useful to have a retry or override or any other option when this behavior occurs.

It has been an easy application to use with my PowerShell scripts that I manage an entire datacenter with.

HashiCorp vault is a simple method to programatically access and maintain secure information (credentials, etc.). I like that it is simple to set up and begin using right away. There are known PowerShell and Perl modules for it, or simply using its API is not all that difficult.

There were some concepts to learn (tokens, keys, hierarchy, and other cool things it does) that needed some explaining, but a co-worker helped me understand, and in less than an hour I was using my first password.

Terraform is great for Infrastructure as Code (IaC), with easy and standardized syntax for provisioning resources within the infrastructure.

Very easy to use, install, manage and update. The system has extensive online documentation and supports many cloud computing services.

It does not have a rollback system in case you accidentally make wrong changes to your infrastructure. Enterprise plans can be expensive, depending on the user's needs.

Terraform well suited for Infrastructure as code utility, and speed ups the deployment of the infrastructure.

- State management - Open source - Not agent based

- Becomes bit tricky when it comes to logic handling.

Terraform supports multiple cloud providers, including AWS, Azure, and Google Cloud Platform, offering flexibility and reducing vendor lock-in.

While Terraform has some rollback mechanisms, they might not be as comprehensive or straightforward compared to specialized rollback solutions.

I have used Terraform for 3 years, I really enjoy using it and helped me get into the DevOps space.

This software is the market leader in IaaS infrastructure deployments, as you can use multicloud deployments, relatively low learning curve, and team will be able to eventually deploy all services and infrastructure using Terraform which is many organization's, is best practice.

There is not much I don't like form this software, is a pleasure to use and different way of approaching IaaS to environements.