Exposing api keys in logs for specific connectors

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

User reports an issue with Airbyte logs displaying api_key values despite setting airbyte_secret to true in spec.yaml. They inquire about known issues in higher versions and seek advice on configuration for specific connectors.


Question

Hello. We’re using Airbyte version 0.50.56 currently.
We found out in our worker logs that it prints out sourceConfiguration with api_keys. This is from ReplicationActivityImpl(lambda$replicateV2$2):162
Initially we thought this was caused by the way we passed in authentication in our source connectors. Then we realized this might be the platform code. Even though we set airbyte_secret as true in spec.yaml, some keys still show up in the logs.
So our questions are:

  1. Is this a known issue? Should any higher version of Airbyte solve this problem?
  2. Since this only happens to 2 of our connectors, did we miss anything in our configurations? All the other connectors don’t have this issue.
    Thanks.

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

['airbyte', 'worker-logs', 'sourceconfiguration', 'api-keys', 'replicationactivityimpl']