You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "jack (JIRA)" <ji...@apache.org> on 2019/07/25 06:34:00 UTC
[jira] [Comment Edited] (AIRFLOW-4917) Add token to S3 credential
to S3ToRedshiftTransfer and RedshiftToS3Transfer
[ https://issues.apache.org/jira/browse/AIRFLOW-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892445#comment-16892445 ]
jack edited comment on AIRFLOW-4917 at 7/25/19 6:33 AM:
--------------------------------------------------------
[~serkef] it is.
AwsHook has aws_session_token.
S3Hook inherit from AwsHook so it's also there.
The operator uses the S3Hook so - what is the problem?
was (Author: jackjack10):
[~serkef] it is.
AwsHook has aws_session_token.
S3Hook inherit from AwsHook so it's also there.
Probebly just need to expose it for the operator.
> Add token to S3 credential to S3ToRedshiftTransfer and RedshiftToS3Transfer
> ---------------------------------------------------------------------------
>
> Key: AIRFLOW-4917
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4917
> Project: Apache Airflow
> Issue Type: Improvement
> Components: aws
> Affects Versions: 1.10.2, 1.10.3
> Reporter: Adrien Marteau
> Priority: Major
>
> When using roles to manage access to S3, in addition to the `access_key` and `secret_key`, you need to pass a `token`.
>
> The current implementation of the S3ToRedshiftTransfer and RedshiftToS3Transfer operators does not allow for that.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)