Glue Catalog Table resource fails to destroy when database cannot be found

[overlordchin]

parent ticket: #19932

Problem statement. When a glue catalog table resource references a database that does not exist (has been destroyed outside of terraform) a terraform destroy will fail with the following error:

Error: Error deleting Glue Catalog Table: EntityNotFoundException: Database mydb not found

Expected behavior - A warning is displayed and the destroy continues to remove the resource as normal.

[github-actions]

This functionality has been released in v3.63.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

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.