https://pulumi.com logo
#general
Title
# general
f

faint-motherboard-95438

12/03/2018, 3:30 PM
Hello here, It seems I got something here. I use
gcp.container.Cluster
to create and manage a cluster with pulumi. I’m still in the learning phase, so I’m doing a lot of trials and errors so I have to update and rebuild the stack often. I changed the way the cluster is named and as expected, pulumi decided to update it (actually, replaced it). But instead of having my new cluster up and running I have now 2 clusters, the new and the old one. I suppose the old one should have been deleted in a replace operation, but it’s actually not (and no error reported about any issue that would have prevented it). I’m well aware that’s not really a daily use case, but anyway, it feels like a bug.
Hum, ok because another thing in the stack when wrong, it didn’t actually deleted it, so now it wants to delete it but since I removed it myself, it fails… not really intuitive.
m

microscopic-florist-22719

12/03/2018, 4:57 PM
can you try running
pulumi refresh
? that should pick up the manual deletion of the cluster.
(we have an issue open to consider doing the
refresh
automatically: https://github.com/pulumi/pulumi/issues/2247)
f

faint-motherboard-95438

12/03/2018, 6:43 PM
yeah, I figured it out, my state wasn’t clean anyway, but an automatic refresh would indeed be great I think, thanks 🙂