You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: