Trying to understand `env` a bit better today ```...
# troubleshooting
v
Trying to understand
env
a bit better today
Copy code
visch@visch-ubuntu:~/git/repo$ meltano --log-level=debug --environment=ci invoke --dump=config tap-postgres-testing
{                                                                                                                                                                                                                                              "sqlalchemy_url": "<postgresql://a>${PG_USER}:${PG_PASSWORD}@${PG_HOST}:${PG_PORT}/postgres_ci_TESTCI"                                                                                                                                       }
Top level envs don't seem to pull in the environment varialbe that is set. ``` environments: - name: dev config: plugins: loaders: - name: target-csv config: timestamp_format: '%Y-%m-%d.T%H%M%S' output_path_prefix: output/ utilities: - name: autoidm-transform - name: prod config: plugins: utilities: - name: autoidm-transform - name: ci env: DBNAME: postgres_ci_${CI_BRANCH} config: plugins: utilities: - name: autoidm-transform #tap-postgres-logs #tap-postgres-testing …
Looks like a bug confimed if I move the top level envs I have
Copy code
#Did mapping purely so env vars would hopefully fail properly
    POSTGRES_USER: a${PG_USER}
    POSTGRES_PASSWORD: ${PG_PASSWORD}
    POSTGRES_HOST: ${PG_HOST}
    POSTGRES_PORT: ${PG_PORT}
To the
<http://environments.ci|environments.ci>
level it works fine
Working on an issue