Terraform TFE Provider version 0.65.0/1 known issue

Problem

The hashicorp/tfe provider versions 0.65.0 and 0.65.1 contain a regression that may cause several known issues. If you are using one of these versions, you may encounter one of the following problems.

Issue 1: tfe_policy_set_parameter Resource Failure

The tfe_policy_set_parameter resource fails with an error related to the schema version when attempting to update the state.

Error: error marshaling prior state: schema version 0 for tfe_policy_set_parameter.policy_set_parameter in state does not match version 1 from the provider

Issue 2: tfe_notification_configuration Validation Failure

The tfe_notification_configuration resource may fail during validation of the url argument.

The attribute 'url' is required when 'destination_type' is '<type>'

Issue 3: tfe_outputs Data Source Panic

The tfe_outputs data source may cause the Terraform process to panic and exit unexpectedly.

Issue 4: tfe_team_token State Corruption

The team_token resource may erroneously remove the token value from the Terraform state during a plan or apply, showing the value changing from a sensitive value to null.

# tfe_team_token.this[0] has changed
~ resource "tfe_team_token" "team_tokens" {
    id    = "team-1234567890abcdef"
  - token = (sensitive value) -> null
    # (1 unchanged attribute hidden)
  }

Cause

A regression was introduced in versions 0.65.0 and 0.65.1 of the hashicorp/tfe provider. Some of these issues have been fixed or reverted in subsequent releases.

Solution

The recommended workaround is to pin the provider version to 0.64.0 to avoid the regression. You can do this by defining a provider version constraint in your Terraform configuration.

Add the following block to your configuration to ensure you are using the stable version.

terraform {
  required_providers {
    tfe = {
      source  = "hashicorp/tfe"
      version = "0.64.0"
    }
  }
}

Additional Information

Once a new version of the provider that addresses these issues is available, you can update your provider version constraint and continue to manage your resources as usual. Monitor the provider's official documentation for release notes.