[jira] [Resolved] (AIRFLOW-48) can't pass extra parameters via a connection URI when using environment variables (and therefore can't tell Postgres to use SSL)

["Fokko Driesprong (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AIRFLOW-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fokko Driesprong resolved AIRFLOW-48.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0
                   1.10.0

Issue resolved by pull request #3292
[https://github.com/apache/incubator-airflow/pull/3292]

> can't pass extra parameters via a connection URI when using environment variables (and therefore can't tell Postgres to use SSL)
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-48
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-48
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: hooks
>    Affects Versions: Airflow 1.7.0
>         Environment: Ubuntu 14.04.3
>            Reporter: Matt Prast
>            Priority: Major
>             Fix For: 1.10.0, 2.0.0
>
>
> We're trying to use a postgres connection to hook into our Redshift backend (which has sslmode set to 'require'). Since we're using chef to deploy we've got the connection string stored in an environment variable, but it looks like the Connection model doesn't parse any connection parameters when it gets initialized with a uri (https://github.com/airbnb/airflow/blob/3c3f5a67ff80f3e8942aef441f481c62baf97184/airflow/models.py#L529). We can't find a way to tell postgres to use SSL without setting sslmode via the connection string, but airflow doesn't seem to allow this, even though you can do it through the UI. Is there something we're missing? Has anybody else run into this using Chef + Postgres + SSL? Thanks for your help!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)