You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Victor Duarte Diniz Monteiro (JIRA)" <ji...@apache.org> on 2017/07/25 02:19:01 UTC

[jira] [Assigned] (AIRFLOW-1342) S3 connections use host "extra" parameter, not Host parameter on connection

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

Victor Duarte Diniz Monteiro reassigned AIRFLOW-1342:
-----------------------------------------------------

    Assignee: Victor Duarte Diniz Monteiro

> S3 connections use host "extra" parameter, not Host parameter on connection
> ---------------------------------------------------------------------------
>
>                 Key: AIRFLOW-1342
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1342
>             Project: Apache Airflow
>          Issue Type: Bug
>    Affects Versions: Airflow 1.8, 1.8.1, 1.8.2
>            Reporter: Bryan Vanderhoof
>            Assignee: Victor Duarte Diniz Monteiro
>            Priority: Trivial
>
> The ability to connect to S3 using Sigv4 was added to resolve AIRFLOW-1034. That implementation expects a "host" parameter to be added to the JSON object in the Extra field on the connection object.
> However, the S3 connection object contains a top-level Host variable, which remains unused. This is deeply counterintuitive. The default should be to leverage this Host variable (and optionally the "host" parameter in the Extra object, to maintain compatibility with the existing implementation).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)