HashiCorp Terraform enables users to define infrastructure as code to safely and predictably codify, plan, and provision any infrastructure. Terraform can provision public cloud resources, private cloud resources, as well as service provider resources like DNS and monitoring to provide a consistent workflow for provisioning.
HashiCorp Terraform Enterprise provides integration with version control systems (VCS) to facilitate collaboration on infrastructure as code. Terraform Enterprise users have been doing version-controlled infrastructure with GitHub and Terraform Enterprise. We are excited to announce the addition of GitLab as a VCS integration with Terraform Enterprise. This post will discuss getting started with Terraform Enterprise and the first steps to setting up GitLab for your environment.
The Terraform CLI works great for individuals, hobby projects, and small teams, but like most CLI tools, it tends to not scale well without a centralized coordination system. The goal of Terraform Enterprise is to simplify using and coordinating Terraform in a team setting. The integrations with version control system such as GitLab are part of Terraform Enterprise. Visit the Terraform Enterprise site to get started.
The first part will be to register Terraform Enterprise as an OAuth Application within your GitLab account.
Once you save the form, you will be redirected to the OAuth Application view. Copy your Application Key and Secret as you will need them to connect GitLab to Terraform Enterprise.
The next part will be inputting your GitLab Application Key and Secret into the Terraform Enterprise UI.
From the Terraform Enterprise UI, you will copy the
Callback URL for your GitLab OAuth Client. Then on GitLab, select the terraform-enterprise OAuth Application. Enter the
Callback URL in the field labeled
To use Terraform Enterprise with GitLab you will need to link to a Terraform Enterprise organization. During the authorization process, there will be a brief redirect to GitLab, from the Terraform Enterprise UI, in order to authenticate the client.
The next part will be to link the Terraform Enterprise User Account. During this authorization process, there will be a redirect to GitLab in order to authenticate your OAuth Client.
In this section you will begin creating HashiCorp Packer Builds and Terraform Environments that are linked to your desired GitLab Repository.
Using the Enterprise UI, you will connect a GitLab Repository to a Terraform Environment. A Menu will appear asking you to name the environment. Then use the autocomplete field for repository and select the repository for which you'd like to create a webhook & environment. If necessary, fill out information about the VCS branch to pull from as well as the directory where the Terraform files live within the repository.
Click Create and Continue.
Upon success, you will be redirected to the environment's runs page. A message will display letting you know that the repository is ingressing from GitLab. When it competes you will be able to Queue, Run, & Apply a Terraform Plan. Depending on your webhook settings, changes will be triggered through git events on the specified branch. The events currently supported are repository and branch push, merge request, and merge.
Using the Enterprise UI, the next part will connect a GitLab Repository to a Packer build configuration. Select the organization for which you'd like to create a build configuration. Name your build & select
Connect build configuration to a Git Repository. A form will appear asking you to select your Git Host. Select your preferred GitLab integration. Choose the repository for which you'd like to create a webhook. Fill out any other information in the form such as preferred branch to build from (your default branch will be selected should this field be left blank), Packer directory, and Packer Template.
Create you will be redirected to the build configuration. On this page, you will have the opportunity to make any changes to your Packer template, push changes via the CLI, or manually queue a Packer build. Depending on your webhook settings, changes will be triggered through git events on the specified branch. The events currently supported are repository and branch push, merge request, and merge.
For complete documentation of the above process, refer to the VCS integration documentation for GitLab.
HashiCorp Terraform provides a consistent approach to provision any infrastructure. This is particularly important for organizations adopting cloud or transitioning to DevOps for application delivery. Consider a resource group on AWS compared to a set of Virtual Machines on Azure. Or a pool of servers on GCP compared to Virtual Machines on vSphere. Conceptually they are all the same and provide infrastructure. The work required to provision and manage them is actually a bit different. Terraform describes infrastructure using a common template in a high-level configuration syntax. The configuration file is then versioned and treated as you would any other code using a VCS. To learn more about our Terraform Enterprise or request a free trial visit www.hashicorp.com/terraform.
The CDK for Terraform 0.5 introduces code generation from HCL and a new cdktf watch workflow for serverless workloads.
Follow our new tutorial to build your summer playlist with Terraform using a community-authored Spotify provider. Hear from the author and share your playlist for a chance to win a free HashiCorp T-shirt.
Learn how to build an automated HashiCorp Vault onboarding system with Terraform using sensible naming standards, ACL policy templates, pre-created application entities, and workflows driven by VCS and CI/CD.