-
Notifications
You must be signed in to change notification settings - Fork 69
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
Cannot Import ACLs using client.KafkaRestEndpoint #528
Comments
I would suggest that this block. Is modified as per something like:
|
Thanks for creating this issue @tthorne-trayport! Could you confirm whether you're using Option 1 or Option 2?
It seems like you're using Option 1 because you're attempting to set IMPORT_KAFKA_REST_ENDPOINT. If that's correct, then we might not want to patch the code since the expectation is that a user doesn't pass
when using Option 1. What do you think? |
Hi @linouk23 - thanks for your response. I am using Option 1, I provide an API Key and Secret via Environment Variables, rather than the provider block. Some context around our deployment: We have a Terraform Directory/Project per Environment (Production, Staging, Test etc.) The Environments have multiple Clusters in them, which poses an issue because in my Deployment Pipeline I can only specify a single Environment Variable per Environment, and therefore cannot have multiple "KAFKA_REST_ENDPOINT"s. This is a problem for me, because my Cluster's within an Environment do not all have the same Rest Endpoints. Therefore, when I provide the Import block:
I am seeing the error:
So my question is, if you are not expecting me to pass "IMPORT_KAFKA_REST_ENDPOINT", which I am not, why am I getting that error? In the situation where "IMPORT_KAFKA_REST_ENDPOINT" is required, and you have multiple Clusters per environment with differing Rest Endpoints I believe you will have to change to a Terraform Directory/Project per Cluster, or Deployment Pipeline/Stage per Cluster to provide this. Which creates a "special case" for ACLs in our deployment model. |
Currently the Import function for the "resource_kafka_acl" resource requires that you set an Environment variable "IMPORT_KAFKA_REST_ENDPOINT"
As per the code in this block.
I would expect that if it cannot find the Environment variable "IMPORT_KAFKA_REST_ENDPOINT" or
client.KafkaRestEndpoint
then it throws an error, but I would prefer that it uses the value provided atclient.KafkaRestEndpoint
so that I can have multiple cluster rest endpoints per set of API Keys.The text was updated successfully, but these errors were encountered: