Do not fail when deleting not existing resource

[EugenKon]

Terraform Version

terraform version
Terraform v1.7.2
on darwin_amd64
+ provider registry.terraform.io/hashicorp/aws v5.15.0
+ provider registry.terraform.io/hashicorp/external v2.3.1
+ provider registry.terraform.io/hashicorp/local v2.3.0
+ provider registry.terraform.io/hashicorp/null v3.2.1

Your version of Terraform is out of date! The latest version
is 1.7.3. You can update by downloading from https://www.terraform.io/downloads.html

Terraform Configuration Files

not required

Debug Output

│ Error: deleting SES Identity Notification Topic (platform-exp.|Bounce): InvalidParameterValue: Identity platform-exp. is invalid. Must be a verified email address or domain.
│ 	status code: 400, request id: 45962f0a-a31a-455c-b7e6-07fb8f94b0ae
│
│
╵
╷
│ Error: deleting SES Identity Notification Topic (platform-exp.|Complaint): InvalidParameterValue: Identity platform-exp. is invalid. Must be a verified email address or domain.
│ 	status code: 400, request id: 0f85c12b-0859-4d4d-85fa-a34aeba31a8f
│
│
╵
╷
│ Error: deleting SES Identity Notification Topic (platform-exp.|Delivery): InvalidParameterValue: Identity platform-exp. is invalid. Must be a verified email address or domain.
│ 	status code: 400, request id: 5b38aed4-38d5-456f-8d00-2814e7891cda
│

Expected Behavior

The resources above does not exists on AWS. I suppose that terraform destroy should not fail.

Actual Behavior

Not relevant error message

Steps to Reproduce

1. Create SES SNS topic and delete it manyally.

Additional Context

No response

References

No response

[apparentlymart]

Hi @EugenKon,

You are describing a behavior of the AWS provider rather than of Terraform Core. Please report this in the AWS provider repository instead. Thanks!

[EugenKon]

@apparentlymart I do not know. I can not distinguish messages from these sources.

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