https://pulumi.com
Join Slack
This message was deleted.
# aws
s
This message was deleted.
s
It gets weirder … if I 
pulumi state delete
the resource urn for the subnet group that comes directly with the error message above, I get the following: 
no such resource exists in current state
l
Looks like the error is coming only form AWS and not Pulumi? Pulumi is all clean but the SubnetGroup and RDS instance are still in AWS?
s
those resources were deleted manually in the aws console though. Are you saying @little-cartoon-10569 that Pulumi is getting the error from an api call to aws to confirm that the subnet group can be deleted? I am not clear whether it is pulumi 
state
or aws 
state
that is the referenced state in 
InvalidDBSubnetGroupStateFault
.
nm - It seems like I had only “stopped” the rds instance and not actually “deleted” it. Once deleted the 
pulumi destroy
cmd worked fine.
It still is confusing to me why pulumi would think it had deleted the rds instance if it wasn’t actually deleted and then try to move on to the related subnets.
l
This is the downside of fully async systems. RDS databases can take a long time to delete, and in many cases, simply will not delete (e.g. if multiAZ is on) but won't tell you immediately. How long does Pulumi wait to find out?
I think most of the time, Pulumi works off the response to the initial request. If Pulumi sends a "delete" request to RDS, and RDS responds with "right-o, I'll get right on that", then Pulumi may have to assume that the DB will eventually be deleted...
s
(A very belated) Thanks @little-cartoon-10569 for the info!
👍 1
4 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by