Athena Database fails to destroy when resources do not exist

[overlordchin]

parent ticket: #19932

Problem statement. When an aws_athena_database resource references a resource that no longer exists(has been destroyed outside of terraform), a terraform destroy will fail with one of the following errors:

Error: Athena not found database: 664df302_mydb, query result: 020dac9f_myquery
Error: reason: FAILED: SemanticException [Error 10072]: Database does not exist: c558ee8f_mydb

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

[overlordchin]

here is is failing on a plan with a similar message:

module.message_bridge.module.athena.aws_athena_database.db: Refreshing state... [id=28ec6a6bmydb]
Error: Athena not found database: 28ec6a6bmydb, query result: 020dac9f_myquery

note that while the DB in question appears different the query result appears the same. This is in a different terraform workspace than the one listed above but seems to suffer from the same issue.

end result is a failed plan

expected behavior - plan detects thing does not exist and either creates it (if the terraform files still describe it) Or doesn't - accordingly.

[github-actions]

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!

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