sparse-intern-71089
08/26/2021, 9:23 AMboundless-car-60268
08/26/2021, 10:41 AMpulumi up
it will perform the instructed updates (create the EKS cluster) then save a json state file. If you then change the code (e.g. to alter the cluster name) and perform pulumi up
again, it will compare what your new code is specifying with the state that it saved the first time around. If they're different it will perform alterations. It may be that it has to delete the original cluster and create a new one.
As your code isn't creating 3 stacks, my guess is that you have run it once and then lost the state somehow before altering the name of the cluster and running it again. Without the state, Pulumi doesn't know what to delete. Your cloud resources from the first run are orphaned and it starts again from scratch creating the new one. Once the resources are orphaned, it's hard to convince Pulumi that it should be managing them and so should delete them when running pulumi destroy
.
Maybe you know all this and I'm barking up the wrong tree. However, if not then please have a read of this: State and Backends | Pulumilate-energy-66663
08/29/2021, 12:07 AM