search

confluentinc / terraform-provider-confluent

Terraform Provider for Confluent
Apache License 2.0
31 stars 64 forks source link

Destroying a KSQLdb cluster leaves a topic behind #401

Open martinrw opened 4 months ago

martinrw commented 4 months ago

If I create a ksqlDB with Terraform it automatically creates a topic for me with a name like "pksqlc-xx123xx-processing-log". If I then destroy this cluster with terraform the ksqldb gets removed as expected but it leaves the topic behind.

Ideally for us this topic would also be removed when the ksqlDB cluster is removed but if that doesn't suit everyone maybe there is an in-between option:

Would it be possible to change the provider to allow for us to define the topic ourselves separately and then point the ksqlDB cluster to use this topic. Then we get the choice whether we want to keep it or not if we delete ksqlDB

linouk23 commented 4 months ago

Thanks for creating the issue @martinrw!

This issue seems to be similar to https://github.com/confluentinc/terraform-provider-confluent/issues/41.