Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airflow.incubator.apache.org
Date: Tue, 19 Jul 2016 17:36:20 +0000 (UTC)
From: "Rob Froetscher (JIRA)" <jira@apache.org>
To: commits@airflow.incubator.apache.org
Message-ID: <JIRA.12990847.1468949762000.74440.1468949780779@Atlassian.JIRA>
In-Reply-To: <JIRA.12990847.1468949762000@Atlassian.JIRA>
References: <JIRA.12990847.1468949762000@Atlassian.JIRA> <JIRA.12990847.1468949762399@arcas>
Subject: [jira] [Created] (AIRFLOW-345) ECS Hook, Operator, Sensor
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 19 Jul 2016 17:36:25 -0000

Rob Froetscher created AIRFLOW-345:
--------------------------------------

             Summary: ECS Hook, Operator, Sensor
                 Key: AIRFLOW-345
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-345
             Project: Apache Airflow
          Issue Type: New Feature
            Reporter: Rob Froetscher
            Assignee: Rob Froetscher
            Priority: Minor


It would be good to have an ECS operator that descends from the AWS hook.

ECS hook, descending from the AWS hook that allows general interaction with ECS
ECS operator to submit a new task definition
ECS operator to kick off a task
ECS operator to update a service with a new task definition
ECS sensor to check on the status of a task

There is a sort of half done one here https://github.com/apache/incubator-airflow/pull/652. But the author says they have abandoned it.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)