-
Notifications
You must be signed in to change notification settings - Fork 61
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
Can't import existing api-keys #17
Comments
@mallie-su thanks for opening an issue! That's very exciting you've proactively migrated to We're thinking about adding an import functionality for One hacky thing you could do right now is to fake an import (I'll use Kafka API Key as an example) by:
(update all IDs including and then run Let me know if it helps! |
The hacky way works like a charm! Not quiet user friendly, espcially with a remote state, but eh, it works! Thanks a lot @linouk23! |
That's great to hear!
For sure, I'll keep this issue open until we add it. |
I'd like to +1 this feature request. I'm in the process of migrating our Confluent configuration to Terraform and it would be great if we could manage all resources, including API keys, in Terraform. |
@mallie-su @sc-alistairdeneys my team discussed this issue internally and I'm happy to let you know that we'll add this functionality in our upcoming |
@mallie-su @sc-alistairdeneys @Talgatele we're happy to let you know that we've implemented import for |
Fantastic! Thanks for the notification @linouk23 |
Hello,
Switching from confluentcloud 0.5.0 went smoothly! Now I want to add support for api key generation.
The problem is: I don't want to recreate existing API keys, as the users of our clusters are actively using them.
The doc doesn't describe how to import the key in our tfstate.
Is there a way to do it? I suppose that's not possible atm, as the error message while trying to import one key is quiet descriptive:
Error: resource confluent_api_key doesn't support import
Is it possible for you to implement it? Or is it "by-design"?
The text was updated successfully, but these errors were encountered: