👋 I was curious utilizing secrets / environment variables within custom connectors. While testing locally, I've been passing in tokens using

docker run -E <secret_token>

to connect to some internal stuff, but I don't want to include these secrets in the

dockerfile

for my connector, as keeping secrets in images is generally bad practice. Also have some specific mounts that I'm currently using with

--mount

Is there a method where I can provide these environment variables when starting up an airbyte instance w/ docker-compose that will be available to the connectors, or what is the suggested workflow for this usecase? I intentionally do not want these to be passed in by the user as part of the

spec.json