terraform 0.12 beta Resource is deleted from state when destroy ends in error

[mark-00]

Terraform Version

>terraform -v
Terraform v0.12.0-beta1
+ provider.google (unversioned)
.

Terraform Configuration Files

...

Debug Output

>terraform apply
google_project.myProject: Refreshing state... [id=testproject]

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  - destroy

Terraform will perform the following actions:

  # google_project.myProject will be destroyed
  - resource "google_project" "myProject" {
      - app_engine          = [] -> null
      - auto_create_network = true -> null
      - id                  = "testproject" -> null
      - name                = "testproject" -> null
      - project_id          = "testproject" -> null
    }

Plan: 0 to add, 0 to change, 1 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

google_project.myProject: Destroying... [id=testproject]

Error: Error deleting project "testproject": googleapi: Error 400: A lien to prevent deletion was placed on the project by [sa-terr@gserviceaccount.com]. Remove the lien to allow deletion., failedPrecondition

>terraform apply
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

Crash Output

Expected Behavior

Terraform should keep trying to delete the resource in a next run if the delete fails

Actual Behavior

the recources is deleted from the state
no new delete attempts are made

Steps to Reproduce

1. create terraform file with google_project
2. terraform apply
3. create lien on project
4. remove project from terraform file
5. terraform apply -> destroy fails
6. terraform apply -> no new attempt for destroy

Additional Context

References

[apparentlymart]

Thanks for reporting this @mark-00!

This issue seems familiar so I think it may already have been addressed since beta1, but I'm not totally sure so we'll use this issue to verify whether it's fixed or if what I'm thinking of was a similar-but-different problem. Thanks again!

[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 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.