Terraform Cloud adds aggregated VCS reviews
Streamline the verification process across multiple workspaces by aggregating status checks directed to external VCS providers and review changes that affect multiple workspaces on a single page.
We are excited to announce the general availability of aggregated VCS reviews, now available for use in HashiCorp Terraform Cloud and coming soon to Terraform Enterprise. This enhancement streamlines the verification process across multiple workspaces by offering an aggregated view of status checks and highlighting the most impactful changes that require the customer's attention before code deployment.
» Status verification challenges
For workspaces linked to a supported version control system (VCS), Terraform Cloud posts status checks back to the repository for runs that occur in response to actions like pull requests (PRs) and merges. These status checks indicate the results of plan/apply runs, policy checks, and run tasks, along with a link back to the corresponding run in Terraform Cloud. This helps ensure the expected result from Terraform changes before code is merged to production and offers valuable in-context feedback for Terraform developers.
However, the previous behavior of sending one check per run did not scale well for customers with monolithic repositories, or monorepos, that contained a large number of workspaces or co-located modules. That approach created an excessive number of status checks, making it difficult to identify essential updates and Terraform plan changes. This highlighted a need for a more efficient way to handle status checks at scale.
» Introducing aggregated VCS reviews
Aggregated reviews address this issue with a consolidated presentation of status checks for monorepos across multiple workspaces, highlighting the most vital changes that require the user’s attention or validation. By highlighting the key changes that could impact infrastructure, the new feature reduces the likelihood of missing unexpected modifications. This concise view of summarized changes also offers a detailed option for more information when needed.
While the key use case of this feature is to streamline the status check process for large-scale monorepos, the enhancement also helps with any Terraform repository connected to many workspaces for the purposes of repeated provisioning across accounts, regions, or environments.
The new feature supports Terraform Cloud’s official VCS integrations including GitHub, GitLab, Bitbucket, and Azure DevOps. The two highlights of this update are:
» An improved commit summary
The upgraded commit summary aggregates status checks by organization, providing a quick overview of proposed changes within all workspaces linked to the repository. Users can access additional information by clicking on a Details link, which leads to the new commit page in Terraform Cloud.
» A new commit page in Terraform Cloud
This page includes comprehensive details of changes linked to each workspace associated with the monorepo, featuring a summary bar that indicates proposed, modified, or destroyed resources. Workspaces are grouped by their status: those that need attention, have resource changes, are still pending, or workspaces with no changes. Users can also filter workspaces by name and project.
» Getting started
This feature can be enabled in the Version Control section of your Terraform Cloud organization settings. To get started, check out the organization settings documentation.
Get started with Terraform Cloud for free to begin provisioning and managing your infrastructure in any environment. Link your Terraform Cloud and HashiCorp Cloud Platform (HCP) accounts together for a seamless sign-in experience.
Sign up for the latest HashiCorp news
More blog posts like this one
HCP Terraform adds run queue visibility and new ephemeral workspace features
HCP Terraform and Terraform Enterprise gain new features related to ephemeral workspaces along with run queue visibility for HCP Terraform specifically.
Automate AWS deployments with HCP Terraform and GitHub Actions
Learn how to use GitHub Actions to automate HCP Terraform operations.
Access AWS from HCP Terraform with OIDC federation
Securely access AWS from HCP Terraform using OIDC federation, eliminating the need to use access keys.