This message was deleted.

sparse-intern-71089

10/07/2020, 2:27 PM

This message was deleted.

chilly-hairdresser-56259

10/07/2020, 3:44 PM

I assume they would cancel a deployment because changes that were seen in preview weren't as expected? I would incorperate a gate of some sort or an approval, after preview returns expected change results then someone approve the actual deployment the

pulumi up

and you can skip the preview since you already seen it.

gorgeous-animal-95046

10/07/2020, 3:49 PM

they would cancel a deployment because it’s stuck, for example. we’re using this for k8s deployments and if the pods don’t come up healthy pulumi just sits there saying it’s working. so users just cancel the job and then it gets in this bad state

kind-mechanic-53546

10/11/2020, 11:50 PM

I also would like guidance on this, I've seen the same thing in CI with k8s and have had to resort to opening the project locally and then doing the export import destroy recreate dance

kind-mechanic-53546

10/11/2020, 11:51 PM

it's not clean and there should be a better way for this to be "production?" ready

kind-mechanic-53546

10/11/2020, 11:51 PM

If you open an issue on github, @gorgeous-animal-95046 , I'd definitely support it (asking for guidance or better tooling support

kind-mechanic-53546

10/11/2020, 11:52 PM

I feel there should be a clean-before-deploy option which nukes any trailing resources before apply

kind-mechanic-53546

10/11/2020, 11:53 PM

(but I'm sure there are smarter folks than I to flesh this out)

2 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.