You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see an issue though - I want to specify mode-specific config eg S3_ETL_BUCKET. If I don't specify this key in the default config, when creating my pipeline with:
dataduct pipeline validate -m production -f test2.yaml
I see the error: "KeyError: 'S3_ETL_BUCKET'. So I must include it eg: etl: S3_ETL_BUCKET: ABC
But the value ABC is then joined to the mode-specific value below: production: etl: S3_BASE_PATH: prod
and the following value is seen in my Pipeline for eg logging: s3://ABC/prod/logs/jeremy_example_upsert/version_20170605153433
This is a bug. Your docs say "Modes define override settings for running a pipeline" but it joins them together instead.
Thanks so much and please help...
The text was updated successfully, but these errors were encountered:
Hi,
Great product!
I see an issue though - I want to specify mode-specific config eg S3_ETL_BUCKET. If I don't specify this key in the default config, when creating my pipeline with:
dataduct pipeline validate -m production -f test2.yaml
I see the error: "KeyError: 'S3_ETL_BUCKET'. So I must include it eg:
etl: S3_ETL_BUCKET: ABC
But the value ABC is then joined to the mode-specific value below:
production: etl: S3_BASE_PATH: prod
and the following value is seen in my Pipeline for eg logging:
s3://ABC/prod/logs/jeremy_example_upsert/version_20170605153433
This is a bug. Your docs say "Modes define override settings for running a pipeline" but it joins them together instead.
Thanks so much and please help...
The text was updated successfully, but these errors were encountered: