You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Kaxil Naik (JIRA)" <ji...@apache.org> on 2018/12/30 00:02:00 UTC
[jira] [Updated] (AIRFLOW-2916) Add argument `verify` for AwsHook()
and S3 related sensors/operators
[ https://issues.apache.org/jira/browse/AIRFLOW-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kaxil Naik updated AIRFLOW-2916:
--------------------------------
Fix Version/s: (was: 2.0.0)
1.10.2
> Add argument `verify` for AwsHook() and S3 related sensors/operators
> --------------------------------------------------------------------
>
> Key: AIRFLOW-2916
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2916
> Project: Apache Airflow
> Issue Type: Improvement
> Components: hooks, operators
> Reporter: Xiaodong DENG
> Assignee: Xiaodong DENG
> Priority: Minor
> Fix For: 1.10.2
>
>
> The AwsHook() and S3-related operators/sensors are depending on package boto3.
> In boto3, when we initiate a client or a resource, argument `verify` is provided (https://boto3.readthedocs.io/en/latest/reference/core/session.html ).
> It is useful when
> # users want to use a different CA cert bundle than the one used by botocore.
> # users want to have '--no-verify-ssl'. This is especially useful when we're using on-premises S3 or other implementations of object storage, like IBM's Cloud Object Storage.
> However, this feature is not provided in Airflow for S3 yet.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)