faint-motherboard-95438
12/03/2018, 3:30 PMgcp.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.microscopic-florist-22719
pulumi refresh
? that should pick up the manual deletion of the cluster.refresh
automatically: https://github.com/pulumi/pulumi/issues/2247)faint-motherboard-95438
12/03/2018, 6:43 PM