-
Notifications
You must be signed in to change notification settings - Fork 12
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
Secret is not properly read in #32
Comments
That sounds like you probably use it incorrectly? But without full logs and configurations, it is hard to be any more specific. |
what kind of logs are you looking for? and which config are you missing? from the kafka connect? |
I guess the logs and configs of where you have this issue? It is not really clear how your setup looks like. If you use Stirmzi, then likely:
|
This is my setup
Here are the configs: and the logs: If you need anything else, I happy to provide more info |
That is neither full logs nor the custom resources as they are in the Kubernetes cluster. You should maybe also check with Apicurio if they support configuration through config providers and how to debug what configuration they get? |
so it could be, that the issue lies with Apicurio? |
I don't know. But that gives you the error. So I think that is the best point to start debugging it to see what it is gettting for data. |
can you give me any pointers on how to debug this? |
No, I gave you the ideas I had above. |
I am using Kafka Connect and have added the config provider like this:
When I use the Secret Provider in my connector (Debezium), it works for some cases but not in others.
Here it works:
But here it doesn't:
the error I get is:
I think this is because it uses
${secrets:kafka-connect/schema-registry-truststore:password}
as string and does not get the secret itself.Does anyone have any idea why it works in the first case but not in the second?
The text was updated successfully, but these errors were encountered: