hello i ve got a stack into a bad state and would love some

Question

hello i ve got a stack into a bad state and would love some help to get it into any sort of different state I can t destroy or make changes to the stack currently I m getting the error ```error pre step event returned an error failed to verify snapshot resource urn pulumi dev lt my stack gt aws cognito userPool UserPool lt my user pool gt dependency refers to missing resource```

bland-byte-34481 · Answer

i ve run `pulumi stack export` and verified that the dependency does in fact exist

little-cartoon-10569 · Answer

The dependency exists in the stack or in AWS

little-cartoon-10569 · Answer

Or both

bland-byte-34481 · Answer

both

little-cartoon-10569 · Answer

Maybe there s a different dependency that is missing Have you checked all of the user pool s dependencies There seems to be a double space in the error message which makes me think that the dependency that is missing is so amazingly missing that Pulumi has forgotten its URN

little-cartoon-10569 · Answer

Since it would have dependecy X refers to missing resource if it was only ordinarily missing slightly smiling face

bland-byte-34481 · Answer

yeah it s only dependency in the stack is a lambda function which exists both in stack and AWS

bland-byte-34481 · Answer

but you re saying the whole thing might have been forgotten

bland-byte-34481 · Answer

the code creating the resource has no additional dependencies either

bland-byte-34481 · Answer

also in the pulumi web console there is no dependency there although it exists in the stack output json

little-cartoon-10569 · Answer

Hmm would there be a delete attribute near the beginning of each resource in the exported state

little-cartoon-10569 · Answer

Or alternatively does `pulumi preview show sames` show that it s going to finish deleting stuff then show a sparse or empty resource tree

bland-byte-34481 · Answer

it shows an update to lamdbaConfig where the missing dependency lies and shows the dependency as delete

little-cartoon-10569 · Answer

Ok that should be an easy fix Make a copy of your exported state find that delete and delete it Usually you can search your state file for ` delete ` and it will find all the things that have been marked for deletion by Pulumi and which Pulumi thinks it has not yet deleted

little-cartoon-10569 · Answer

Those lines should all be very near the top of their respective resource definitions maybe in the top 3 or 4 lines

little-cartoon-10569 · Answer

If you delete the offending ones in the copy of your state file and import that copy hopefully it ll stop trying to delete them and consider them still in the resource dependency tree

little-cartoon-10569 · Answer

In case it s not clear the things you want to delete are just the lines ` delete true `

little-cartoon-10569 · Answer

Or something like that I don t have an example here

bland-byte-34481 · Answer

that may have steered me to a solution thank you < little cartoon 10569> raised hands