postconditions prevent destroy

[azrdev]

Terraform Version

Terraform v1.3.3
on linux_amd64
+ provider registry.terraform.io/hashicorp/null v3.2.0
+ provider registry.terraform.io/vmware/vra v0.6.0

Terraform Configuration Files

terraform {
  required_version = ">= 1.3.0"
  required_providers {
    vra = {
      source  = "vmware/vra"
      version = ">= 0.5.1"
    }
  }
}
resource "vra_deployment" "vm" {
  name = "test"
  catalog_item_name = "test"
  lifecycle {
    postcondition {
      condition     = self.last_request[0].action_id != "Deployment.Expire"
      error_message = "Machine has been Expired by vRA"
    }
  }
}

Debug Output

│ Error: Resource postcondition failed

Expected Behavior

The postcondition should fail in this case. But it should not prevent destruction of the resource.

Actual Behavior

terraform destroy fails instead of destroying the resource

Steps to Reproduce

1. terraform init
2. terraform destroy

Additional Context

Putting the check as a precondition on an output value (which should be calculated after changes to the resource) still fails terraform destroy.

References

• Allow lifecycle replace_triggered_by to trigger on any string change #31685
• Add support to filter/taint expired deployments to trigger recreation vmware/terraform-provider-vra#473

[jbardin]

Closed via #32051

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.