Can't destroy a module without optional field being set at time of creation

[hashibot]

This issue was originally opened by @selslack as hashicorp/terraform#13328. It was migrated here as part of the provider split. The original body of the issue is below.

---

Hello!

Terraform Version

Terraform v0.9.2

Affected Resource(s)

Please list the resources as a list, for example:

• google_compute_address
• google_compute_global_address
• google_compute_instance

Maybe others with optional fields defaulting to something computed.

Expected Behavior

Resources created by that module are destroyed.

Actual Behavior

Error "project": required field is not set.

Steps to Reproduce

1. Create a module with GCE resources listed above without optional field project set
2. terraform apply
3. Remove that module from definition
4. terraform plan

[rosbo]

This issue was fixed by #784 and release in google terraform provider version 1.3.0

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!