This message was deleted.

sparse-intern-71089

02/02/2021, 5:26 PM

This message was deleted.

gentle-diamond-70147

02/02/2021, 6:50 PM

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?

elegant-island-39916

02/02/2021, 7:24 PM

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

elegant-island-39916

02/02/2021, 7:26 PM

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

gentle-diamond-70147

02/02/2021, 8:06 PM

The resources still exist at aws and k8s, right? Only deleted from your state?

9 Views

Open in Slack

Previous Next

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.