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/05/14 18:52:00 UTC
[jira] [Resolved] (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:all-tabpanel ]
Kaxil Naik resolved AIRFLOW-2435.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.10.0
Issue resolved by pull request #3329
[https://github.com/apache/incubator-airflow/pull/3329]
> 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
> Fix For: 1.10.0
>
>
> 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)