dan_ladd
02/04/2021, 4:56 PM$MELTANO_PROJECT_ROOT/client_secrets.json
douwe_maan
02/04/2021, 5:02 PMcredentials_path
setting to an empty string (""
), is that enough to make target-bigquery / google-cloud-bigquery ignore it and fall back on the default?
meltano config target-bigquery set credentials_path ""
dan_ladd
02/04/2021, 5:14 PMmeltano | Loading failed (1): google.auth.exceptions.DefaultCredentialsError: File was not found.
douwe_maan
02/04/2021, 5:33 PMcredentials_path: null
in meltano.yml
won't work either because Meltano will just fall back on the default value.
As a workaround for now, I suggest copying the entire plugin definition (https://gitlab.com/meltano/meltano/blob/master/src/meltano/core/bundle/discovery.yml#L1039-1088) into your meltano.yml
so Meltano will treat it as a custom plugin, and then deleting the default value
for credentials_path
. With the optional bits removed:
- name: target-bigquery
namespace: target_bigquery
variant: adswerve
pip_url: git+<https://github.com/adswerve/target-bigquery.git@v0.10.2>
dialect: bigquery
target_schema: $TARGET_BIGQUERY_DATASET_ID
settings:
- name: project_id
- name: dataset_id
value: $MELTANO_EXTRACT__LOAD_SCHEMA
- name: location
value: US
- name: credentials_path
env_aliases: [GOOGLE_APPLICATION_CREDENTIALS]
- name: validate_records
kind: boolean
value: false
- name: add_metadata_columns
kind: boolean
value: false
- name: replication_method
kind: options
options:
- label: Append
value: append
- label: Truncate
value: truncate
value: append
- name: table_prefix
- name: table_suffix
- name: max_cache
value: 50
douwe_maan
02/04/2021, 5:34 PMnull
in meltano.yml
? If we support that, the env var wouldn't populated at all with credentials_path: null
, and we'd have the desired result.dan_ladd
02/04/2021, 7:17 PMdouwe_maan
02/04/2021, 8:39 PM