Chicken and Egg about terraform-provider-kafka

[Mongey]

👋 @paulca99 I don't believe this is an issue with this particular provider; and is more of a terraform question.
When destroying the cluster, doing a terraform destroy should remove the topics, then destroy the ec2 instances. If you are rotating the instances outside of terraform, doing a terraform refresh once the new cluster is up, should be enough to get terraform to notice that the topics don't exist on the new kafka cluster; and a subsequent plan and apply should work.

[paulca99]

I can't do a terraform destroy as there's a load of other resources in the same env that I don't want to destroy. TBH I've just had 2 weeks off work and it's a bit fuzzy in my head, I'll try the refresh route on Monday when I go back in, but I think once the EC2 instances had been destroyed outside terraform , and the provider couldn't create a connection to kafka I was snookered because I couldn't re-create the cluster with a terraform apply... but I never tried the refresh, so I'll try that first...ta.

[Mongey]

Going to close this out as there's not much I can fix here 😄