[ACTION REQUIRED] Pin current version of HCP Terraform Provider to account for upcoming changes to networking resources

We have recently released new networking capabilities for HashiCorp Cloud Platform. To accommodate these features, we will be introducing breaking changes to resources in the HCP Terraform Provider.

The changes will occur in the coming days. Action is required on your part to avoid disruption to workflows that use this Provider. We have included details about these changes and how to account for them below.

WHAT IS HAPPENING?
We are introducing breaking changes to hcp_aws_network_peering and hcp_aws_transit_gateway_attachment resources in the HCP Terraform Provider.

IS MY HCP DEPLOYMENT AFFECTED?
No. This change does not impact your services running on HCP. It only affects the HCP Terraform Provider.

WHAT ACTION DO I NEED TO TAKE?
To avoid disruption, you will need to β€œpin” the current version of the HCP Terraform Provider in your workflows. To do this, simply use the = operator when specifying the version in your .tf files.

In this case, your syntax would be as follows:

terraform {
  required_providers {
    hcp = {
      source  = "hashicorp/hcp"
      version = "0.6.0"
    }
  }
}

You can read more about pinning in the Terraform documentation.

We do not anticipate this action being difficult for most users. If you do have questions, please contact us via the HashiCorp Help Center.

WHY IS THIS HAPPENING?
These changes will enable HashiCorp Cloud Platform to support more flexible network topologies, enabling both VPC peering and Transit Gateway attachment.

WHEN IS THIS HAPPENING?
These resource changes are already live in the HashiCorp Cloud Platform UI. We will be deploying the changes to the HCP Terraform Provider no sooner than June 8, 2021.

WHAT HAPPENS AFTER THE HCP TERRAFORM PROVIDER IS CHANGED?
We will publish a new version of the HCP Terraform Provider. The pinning technique described above will help you avoid disruption in the near term. But later in June - after the updates - you will need to take additional steps to account for these changes your HCL. We will provide additional documentation in the coming days on how to perform these steps.

If you have any questions, please feel free to contact us via the HashiCorp Help Center.

Thank you.

Trevor Powell
Product Manager :heart: HCP Terraform Provider

2 Likes

Hello, Please see the follow up post about cool new changes for the Provider and how to navigate the breaking changes.