Closed antoniordz96 closed 1 year ago
Thanks for reporting this,
Could you post some clearer reproduction steps, ideally code that I can copy+paste? It's not clear to me how exactly you have this resource configured, it sounds like you're deploying to multiple regions?
This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.
Describe the bug
We are deploying a multi region API with a route53 recordSet as shown below.
The stack creates successfully in the east region but fails to provision in the west region as it seems the custom resource is attempting to delete a non-existing record.
We believe we have tracked this down to the following request listResourceRecordSets in the custom resource which returns the A record set in us-east-1. The custom resource proceeds to attempt delete the A record and fails.
Expected Behavior
The custom resource on creation should not attempt to delete A non existent A record in the region
Current Behavior
Stack creation in second region fails to provision due to custom resource not being able to delete A record.
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.77.0
Framework Version
No response
Node.js Version
v16.16.0
OS
Mac
Language
Typescript
Language Version
No response
Other information
No response