You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/05/14 18:51:00 UTC

[jira] [Commented] (AIRFLOW-2435) Add launch_type to ECSOperator to allow FARGATE

    [ https://issues.apache.org/jira/browse/AIRFLOW-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474621#comment-16474621 ] 

ASF subversion and git services commented on AIRFLOW-2435:
----------------------------------------------------------

Commit 776669ab60d92f56d1f1804b003ad4372c13cbfa in incubator-airflow's branch refs/heads/master from [~ThomasVdBerge]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=776669a ]

[AIRFLOW-2435] Add launch_type to ECSOperator to allow FARGATE

Closes #3329 from ThomasVdBerge/ecs-fargate


> Add launch_type to ECSOperator to allow FARGATE
> -----------------------------------------------
>
>                 Key: AIRFLOW-2435
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2435
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: DagRun
>    Affects Versions: 1.9.0
>            Reporter: Thomas Van den Berge
>            Assignee: Thomas Van den Berge
>            Priority: Critical
>
> Currently we can start ECS tasks via the task definition on EC2.
> It would be cool if we could also supply an extra parameter, launch_type, to launch the airflow tasks on FARGATE.



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