This message was deleted.
# general
s
This message was deleted.
c
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.
g
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
k
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
it's not clean and there should be a better way for this to be "production?" ready
If you open an issue on github, @gorgeous-animal-95046 , I'd definitely support it (asking for guidance or better tooling support
I feel there should be a clean-before-deploy option which nukes any trailing resources before apply
(but I'm sure there are smarter folks than I to flesh this out)