I’m using the

aws:region

configuration to configure my stacks. A stack was deployed to

us-east-1

then the

aws:region

was swapped to

us-west-2

and deployed. It got half way through and then failed. It now fails to delete any resources from either region and returns errors like:

error reading ELBv2 Target Group [omitted] is not a valid target group ARN

and

InvalidParameterException: Invalid Region in ARN

What’s the best way to reconcile this without deleting all the resources manually then force deleting the stack? Thank you!

The thing I’d try first would be

pulumi refresh

, probably with

us-east-1

first, and assuming that worked, then destroying and repeating with

us-west-2

. Have you tried that?

Sorry for the late reply! I tried pulumi refresh individually for both regions and neither worked. I think the mix of resources recorded in each region causes the “invalid ARN” error and it blocks the refresh. Perhaps this wouldn't fix it but, is there any way to ignore errors with refresh and just refresh the resources that didn't error?