Skip ValidateResourceConfig when the resource is only being destroyed

[vladimirtiukhtin]

Terraform Version

Terraform v1.5.1
on linux_amd64

Terraform Configuration Files

...terraform config...

Debug Output

│ Error: versioning_configuration.status cannot be updated from 'Enabled' to 'Disabled'

Expected Behavior

When destroy is called terraform should not perform any validation and just delete target objects

Actual Behavior

Checks are done as it seems

Steps to Reproduce

1. Create an S3 bucket link aws_s3_bucket_versioning resource to it
2. Modify aws_s3_bucket_versioning (only code)
3. Run terraform destroy

Additional Context

No response

References

No response

[jbardin]

Hi @vladimirtiukhtin,

Thanks for filing the issue. This is currently expected, since there are elements of the configuration which do come into play even during a destroy operation. We also need to take into account that providers expect all resources to be read before they are destroyed, which currently requires a normal plan to be executed internally before the destroy plan is constructed.

Because the validation and destroy plan happen in different phases of execution it makes the change a bit more difficult, but I'm going to update this to an enhancement request to see if that change can be made at all.

Thanks!