Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Destroying a KSQLdb cluster leaves a topic behind #401

Open
martinrw opened this issue Jul 3, 2024 · 1 comment
Open

Destroying a KSQLdb cluster leaves a topic behind #401

martinrw opened this issue Jul 3, 2024 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@martinrw
Copy link

martinrw commented Jul 3, 2024

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
Copy link
Contributor

Thanks for creating the issue @martinrw!

This issue seems to be similar to #41.

@linouk23 linouk23 added the duplicate This issue or pull request already exists label Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants