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
Warning:"ca_cert_file": [DEPRECATED] This parameter is now deprecated and will be removed in a later release, please use `ca_cert` instead.
Warning:"client_cert_file": [DEPRECATED] This parameter is now deprecated and will be removed in a later release, please use `client_cert` instead.
Warning:"client_key_file": [DEPRECATED] This parameter is now deprecated and will be removed in a later release, please use `client_key` instead.
This is confusing as I'm not using the configuration parameters in provider - neither old names nor new ones.
Looks like this is happening because both old and new config parameters are mapped to the same environment variables, e.g.
Is it supposed to work like that ?
The text was updated successfully, but these errors were encountered:
Looks like this is happening because both old and new config parameters are mapped to the same environment variables
Specifically:
ca_cert_file is deprecated and reads from the KAFKA_CA_CERT env var
Per the deprecation we should use ca_cert instead, but this also reads from KAFKA_CA_CERT
So if you set KFAKA_CA_CERT I guess both get set, resulting in a deprecation warning from ca_cert_file.
I wonder if this can be avoided by adding another env var for ca_cert (the naming is a bit unfortunate, since the deprecated var already makes use of KAFKA_CA_CERT which is what ca_cert would naturally map to):
I'm using environment variables to pass credentials to Kafka provider, e.g.
Provider configuration :
when I ran the plan I get this:
This is confusing as I'm not using the configuration parameters in provider - neither old names nor new ones.
Looks like this is happening because both old and new config parameters are mapped to the same environment variables, e.g.
Is it supposed to work like that ?
The text was updated successfully, but these errors were encountered: