Hello 👋. Hoping someone could help with running on GCP. I want to run a meltano docker container on Airflow (in Cloud Composer). I’ve gotten tap-purecloud to target-bigquery working locally and it inserts records to BigQuery fine. However locally I’m using a service account json key file for BigQuery permission and it wouldn’t be good practice to have that in the container image. I’m thinking I could pass the content of that key file as an environment variable then write it to target-bigquery’s expected default location,

project/client_secrets.json

. That seems pretty inelegant though. I’m new to docker/containers so am wondering if there’s a better approach?

Hi Mark. I'm not that familiar with Cloud Composer, but the normal Kubernetes approach is to use secrets - these can be mounted as files or used to populate environment variables: https://kubernetes.io/docs/concepts/configuration/secret/#using-secrets Perhaps these docs for Cloud Composer are helpful: https://cloud.google.com/composer/docs/secret-manager One question for my own "market research" if you're up for it - is the Cloud Composer infrastructure just doing this one sync or are you already running lots of pipelines and this tap-purecloud -> target-bigquery if one of many?

Hi Aaron. Thanks for those links, mounting a file sounds like what I want to do. We already have a good few (like 15ish) DAGs running on Cloud Composer. They mostly run dbt cleaning but some are custom extract and load pipelines. This would be our first use of Meltano.