provider/aws: aws_route53_zone with force_destroy fails to delete zone on destroy

[ryane]

Terraform Version

$ terraform version
Terraform v0.8.8

Affected Resource(s)

• aws_route53_zone

Terraform Configuration Files

provider "aws" {
  region = "us-east-1"
}

resource "aws_route53_zone" "public" {
  name          = "myexample.com."
  force_destroy = true
}

output "zone_id" {
  value = "${aws_route53_zone.public.id}"
}

Debug Output

https://gist.github.com/ryane/ba584cdb3023b4f02dfe9cb4dfb2225a

Expected Behavior

It is my understanding that setting force_destroy = true should tell Terraform to delete all records in the zone when it destroys the resource even if it contains records that are not managed by Terraform.

Actual Behavior

Destroying fails with this error:

* aws_route53_zone.public: HostedZoneNotEmpty: The specified hosted zone contains non-required resource record sets  and so cannot be deleted.
        status code: 400, request id: e466d633-0014-11e7-a009-8d1bd2e9a272

Steps to Reproduce

1. Run terraform apply. This should complete successfully.
2. Create a record in the zone that is outside of Terraform control. For example:

create.json:

{
  "Comment": "Create an A record",
  "Changes": [
    {
      "Action": "UPSERT",
      "ResourceRecordSet": {
        "Name": "test.myexample.com.",
        "Type": "A",
        "TTL": 300,
        "ResourceRecords": [
          {
            "Value": "8.8.8.8"
          }
        ]
      }
    }
  ]
}

$ aws route53 change-resource-record-sets \
   --hosted-zone-id $(terraform output zone_id) \
   --change-batch file://create.json

3. Run terraform destroy

$ terraform destroy -force
aws_route53_zone.public: Refreshing state... (ID: Z273D4PE6ATWJH)
aws_route53_zone.public: Destroying...
Error applying plan:

1 error(s) occurred:

* aws_route53_zone.public: HostedZoneNotEmpty: The specified hosted zone contains non-required resource record sets  and so cannot be deleted.
        status code: 400, request id: e466d633-0014-11e7-a009-8d1bd2e9a272

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

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