Bug report

The Debezium connector for postgresql seems to ignore the DirectoryConfigProvider from Kafka connect.

What Debezium connector do you use and what version?

debezium-connector-postgresql:2.0.1

What is the connector configuration?

config.providers: directory
config.providers.directory.class: org.apache.kafka.common.config.provider.DirectoryConfigProvider
database.user: '${directory:/PATH/TO/MOUNTED/SECRET:DB_USERNAME}'
database.password: '${directory:/PATH/TO/MOUNTED/SECRET:DB_PASSWORD}' 

What is the captured database version and mode of deployment?

On-premise

What behaviour do you expect?

Using the mounted kubernetes secret from the files within the configured directory

What behaviour do you see?

The connector seems to ignore the DirectoryConfigProvider settings. Instead, the following error will be thrown:

connect Rest API request failed: Connector configuration is invalid and contains the following 1 error(s):
Error while validating connector config: FATAL: password authentication failed for user "${directory:/PATH/TO/MOUNTED/SECRET:DB_USERNAME}" 

When reconfiguring the config.providers section to file and creating a secrets file int the format the config provider expects, everything works fine.

Do you see the same behaviour using the latest relesead Debezium version?

Could test with the 2.0.1 version only, newer versions are still missing in the Confluenthub.

Do you have the connector logs, ideally from start till finish?

see "Behaviour" section above.

How to reproduce the issue using our tutorial deployment?

Use the configuration snippet provided in "connector configuration" above.