What is your primary use case for HashiCorp Terraform?

I use the solution to provision cloud resources on Azure, AWS, and GCP platforms.

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

It is a useful configuration management solution. DevOps practices are a main tool for infrastructure as a code.

We use HashiCorp Terraform for Infrastructure as Code. It automates the deployment of infrastructure within the Azure platform. Terraform can manage almost all aspects of infrastructure provisioning. If there are tasks that Terraform cannot perform directly, you can use the Azure CLI or other tools and call them from within Terraform scripts.

HashiCorp Terraform is primarily used to manage infrastructure. It is responsible for creating and managing infrastructure components. For example, when we initially designed the infrastructure for this project, we started by designing the VPC. We decided to use a specific region-based VPC. We specified the number of public and private subnets, as well as setting up Internet gateways and NAT gateways, all using Terraform. Once the infrastructure was set up, we deployed our resources, such as ECS containers, ECS tasks, and RDS databases, in private subnets, all properly managed by Terraform. However, we use GitHub Actions for CI/CD pipeline purposes. While Terraform handles the infrastructure management, GitHub Actions manages the CI/CD pipeline for our ECS clusters. In my previous project, we used Jenkins, but in this project, we use GitHub Actions for deployment, testing, and other pipeline tasks.

I use the solution in my company to create services over cloud platforms. I have used HashiCorp Terraform for GCP, Azure, and AWS to create resources. With HashiCorp Terraform, it is easy to manage resources in a single file.

We use Terraform for many different use cases. The primary one is ensuring that the security policy is automatically applied to all of the resources within a cloud environment. Another one would be creating and dismantling all sorts of test labs, as well as creating a development environment. We found a way to automatically create a development environment only for the time we need. We develop the infrastructure and cloud-related tasks.

My company uses HashiCorp Terraform for cloud infrastructure provisioning. HashiCorp Terraform is the only IaC tool we use in our company.

Terraform is our main infrastructure as code at the bank. Our entire deployment site and the AWS solution are based on Terraform. We use EBridge and the Dochub solution on the Bitbucket pipeline. Terraform runs on a container in the Bitbucket pipeline, but to create my entire cloud solution, I use EBridge.

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.

We use it to deploy resources on AWS.

We use the solution for provisioning.

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.

Our company uses the solution to deploy resources and infrastructure in Azure Cloud via the Azure DevOps pipelines. We have two developers who use the solution.

HashiCorp Terraform is a tool used for provisioning cloud infrastructure. It is used in this specific use case to deploy and provision all services, including Kafka, MongoDB, and Postgres clusters, using infrastructure as code.

We have about 50 users.

Initially, We have started using Terraform for provision cloud infrastructure and slowly our requirement keep growing up currently my team is using Terraform for managing AWS/Azure/GCP or I should multiple clouds along with Kubernetes/Rancher, Gitlab, MySQL/Oracle, datadog.

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.

We use HashiCorp Terraform to set up AWS infrastructure, and sometimes Cloudflare. It is not exactly a tool for configuration, it is for setting up the development of the infrastructure.

We use HashiCorp Terraform to deploy applications and infrastructures.

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.

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

A primary use case of Terraform is for deploying a VM on a cloud using Terraform script. If I then want to deploy a third-party toolset, a solution such as Aviatrix can create an overlay on top of each of the cloud providers and you can connect the clouds together. I'm a solutions architect and we are customers of HashiCorp.

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

I use the latest version.

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

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.

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.

We deliver the platform as a service to businesses. For example, one request for a particular subscription could be in the business domain or non-business domain, whatever it may be, based on the demand, we deliver the customized subscription to them. For each service, we have different constraints. What needs to be delivered in the VNet of Azure, and what needs to be done externally.

We use it to provision cloud infrastructure. We use it to provision all kinds of infrastructure from wherever we want, we Terraform to the cloud. We provision new infrastructure, we update existing infrastructure with it, we manage our DNS records, and also deploy new applications on Kubernetes. That's the main use, but we use it for all of our infrastructures, so it has a lot of different use cases.