This message was deleted.
# general
s
This message was deleted.
g
Hi, I'm very sorry for that. That's certainly not what should happen or the behavior you should expect. Can you elaborate more on your environment and how this happened? - What providers you're using? - How long the
up
ran before failing? - Was the
up
canceled or did it error and fail on its own? - What state backend you're using?
e
I'm using S3 state backend, it appears not all items in my state were deleted. Only those that were nested in an apply of
pulumi.Output.all(...).apply(...)
while requiring multiple outputs from one
StackReference
. My internet has been a bit choppy today, so I believe those timeout errors I saw are from the stack references not being retrieved and therefore not spinning up the resources from within the apply
1. providers: aws and k8s (eks) 2. up took 2m10s 3. it seemed to continue to delete everything within the apply 4. state backend is S3
g
The resources still exist at aws and k8s, right? Only deleted from your state?