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

big-article-88775

03/20/2019, 6:38 PM
After that, I deleted the cluster manually in AWS, and tried to use
pulumi destroy
to clean up the miscellaneous other objects... but Pulumi again choked on removing the namespace, because now it couldn't talk to the cluster. I would like to see Pulumi be smarter here, recognize the cluster is gone so the dependent objects are also gone and help me remove the miscellaneous other objects.
@gorgeous-egg-16927 should we create an issue for this as well, as it is a slightly different problem?
actually this looks like it is the same as this second aspect https://github.com/pulumi/pulumi-kubernetes/issues/416
g

gorgeous-egg-16927

03/20/2019, 8:19 PM
yeah, that’s right