[Bug] Printing of secrets to console when creating a delta lake sink

[szindel]

Search before asking

• I searched in the issues and found nothing similar.

Read release policy

• I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

Version

Ran on the apachepulsar/pulsar:3.0.10 docker.

• OS: Ubuntu 22.04.5
• Java: 17.0.14
• Pulsar version: 3.0.10
• Deployment: standalone and cluster
• Connector: pulsar-io-lakehouse-3.0.7.5-cloud.nar

Minimal reproduce step

0. Startup any pulsar cluster
1. configure a sink (for example delta lake sink) with a SimpleAWSCredentialProvider
2. create the sink
3. output shows the entire config: including secrets

What did you expect to see?

Either to not have the secrets being printed to the console/stdout or have it anonymised with ******
Or, an way to pass environment variables to the kubernetes runtime in the sink create statement (via sink-config), so the EnvironmentCredentialProvider can be used for kubernetes runtimes.

What did you see instead?

The entire config of the sink with secrets printed to the console: quite undesirable.

Anything else?

It would be ideal to have a way of setting environment variables in the kubernetes runtime (not secrets, but just simple env vars). Being able to pass these via the config.

Are you willing to submit a PR?

• I'm willing to submit a PR!