[jira] [Commented] (AIRFLOW-3537) Allow AWS ECS Operator to use templates in task_definition parameter

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on AIRFLOW-3537:
-----------------------------------------

tomoyat opened a new pull request #4341: [AIRFLOW-3537] Add task_definition as templated parameter in AWS ECS Operator
URL: https://github.com/apache/incubator-airflow/pull/4341
 
 
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [x] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
     - https://issues.apache.org/jira/browse/AIRFLOW-3537
     - In case you are fixing a typo in the documentation you can prepend your commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
   
   ### Description
   
   - [x] Here are some details about my PR, including screenshots of any UI changes:
   
   When using the AWS ECS Operator, I'd like to pass the task_definition as a template. Because I decide the task_definition dynamically by another operator, and get the task_definition from XCom.
   
   ### Tests
   
   - [x] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   
   Updated existing test case to check for new field.
   
   
   ### Commits
   
   - [x] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [x] In case of new functionality, my PR adds documentation that describes how to use it.
     - When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.
     - All the public functions and the classes in the PR contain docstrings that explain what it does
   
   ### Code Quality
   
   - [x] Passes `flake8`
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Allow AWS ECS Operator to use templates in task_definition parameter
> --------------------------------------------------------------------
>
>                 Key: AIRFLOW-3537
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3537
>             Project: Apache Airflow
>          Issue Type: Wish
>          Components: aws
>            Reporter: tomoya tabata
>            Assignee: tomoya tabata
>            Priority: Minor
>
> The AWS ECS operator does not currently apply templates to the task_definition parameter.
> I'd like to allow AWS ECS Operator to use templates in task_definition parameter.



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