Open WafflesMcDuff opened 3 years ago
I see exactly the same behavior.
Same here
Hmm wonder if we need to create a service linked role as a resource managed by this TF config in order so that destroy removes it?
@bflad - Who is the right person to tag for LakeFormation issues?
I had the same issue, tried rerunning my apply and seems to have worked. Anyone with the same experience ?
Simulated @abhihashi 's retry as a stop gap to standup and terardown cleanly until a permanent fix is applied in a buildkite pipeline. ``
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.
If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!
Community Note
Terraform CLI and Terraform AWS Provider Version
Terraform v0.13.6
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
Panic Output
Expected Behavior
terraform should be able to apply and destroy
Actual Behavior
apply works, destroy returns this error:
Error: error deregistering Lake Formation Resource (arn:aws:s3:::mybucket): InvalidInputException: Must manually delete service-linked role to deregister last S3 location.
Steps to Reproduce
terraform apply
terraform destroy
Important Factoids
References