{"action":"created","issue":{"url":"https://api.github.com/repos/apache/incubator-airflow/issues/3908","repository_url":"https://api.github.com/repos/apache/incubator-airflow","labels_url":"https://api.github.com/repos/apache/incubator-airflow/issues/3908/labels{/name}","comments_url":"https://api.github.com/repos/apache/incubator-airflow/issues/3908/comments","events_url":"https://api.github.com/repos/apache/incubator-airflow/issues/3908/events","html_url":"https://github.com/apache/incubator-airflow/pull/3908","id":360698482,"node_id":"MDExOlB1bGxSZXF1ZXN0MjE1ODU3MDQ3","number":3908,"title":"[AIRFLOW-3036] Add relevant ECS options to ECS operator.","user":{"login":"jmcarp","id":1633460,"node_id":"MDQ6VXNlcjE2MzM0NjA=","avatar_url":"https://avatars0.githubusercontent.com/u/1633460?v=4","gravatar_id":"","url":"https://api.github.com/users/jmcarp","html_url":"https://github.com/jmcarp","followers_url":"https://api.github.com/users/jmcarp/followers","following_url":"https://api.github.com/users/jmcarp/following{/other_user}","gists_url":"https://api.github.com/users/jmcarp/gists{/gist_id}","starred_url":"https://api.github.com/users/jmcarp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jmcarp/subscriptions","organizations_url":"https://api.github.com/users/jmcarp/orgs","repos_url":"https://api.github.com/users/jmcarp/repos","events_url":"https://api.github.com/users/jmcarp/events{/privacy}","received_events_url":"https://api.github.com/users/jmcarp/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-09-17T01:12:39Z","updated_at":"2018-09-20T15:39:46Z","closed_at":"2018-09-17T12:59:09Z","author_association":"CONTRIBUTOR","pull_request":{"url":"https://api.github.com/repos/apache/incubator-airflow/pulls/3908","html_url":"https://github.com/apache/incubator-airflow/pull/3908","diff_url":"https://github.com/apache/incubator-airflow/pull/3908.diff","patch_url":"https://github.com/apache/incubator-airflow/pull/3908.patch"},"body":"Make sure you have checked _all_ steps below.\r\n\r\n### Jira\r\n\r\n- [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\"\r\n  - https://issues.apache.org/jira/browse/AIRFLOW-XXX\r\n  - 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.\r\n\r\n### Description\r\n\r\n- [x] Here are some details about my PR, including screenshots of any UI changes:\r\n\r\nThe ECS operator currently supports only a subset of available options\r\nfor running ECS tasks. This patch adds all ECS options that could be\r\nrelevant to airflow; options that wouldn't make sense here, like\r\n`count`, were skipped.\r\n\r\n### Tests\r\n\r\n- [x] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:\r\n\r\n### Commits\r\n\r\n- [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/)\":\r\n  1. Subject is separated from body by a blank line\r\n  1. Subject is limited to 50 characters (not including Jira issue reference)\r\n  1. Subject does not end with a period\r\n  1. Subject uses the imperative mood (\"add\", not \"adding\")\r\n  1. Body wraps at 72 characters\r\n  1. Body explains \"what\" and \"why\", not \"how\"\r\n\r\n### Documentation\r\n\r\n- [x] In case of new functionality, my PR adds documentation that describes how to use it.\r\n  - When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.\r\n\r\n### Code Quality\r\n\r\n- [x] Passes `git diff upstream/master -u -- \"*.py\" | flake8 --diff`\r\n"},"comment":{"url":"https://api.github.com/repos/apache/incubator-airflow/issues/comments/423231025","html_url":"https://github.com/apache/incubator-airflow/pull/3908#issuecomment-423231025","issue_url":"https://api.github.com/repos/apache/incubator-airflow/issues/3908","id":423231025,"node_id":"MDEyOklzc3VlQ29tbWVudDQyMzIzMTAyNQ==","user":{"login":"smith-m","id":23284218,"node_id":"MDQ6VXNlcjIzMjg0MjE4","avatar_url":"https://avatars0.githubusercontent.com/u/23284218?v=4","gravatar_id":"","url":"https://api.github.com/users/smith-m","html_url":"https://github.com/smith-m","followers_url":"https://api.github.com/users/smith-m/followers","following_url":"https://api.github.com/users/smith-m/following{/other_user}","gists_url":"https://api.github.com/users/smith-m/gists{/gist_id}","starred_url":"https://api.github.com/users/smith-m/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/smith-m/subscriptions","organizations_url":"https://api.github.com/users/smith-m/orgs","repos_url":"https://api.github.com/users/smith-m/repos","events_url":"https://api.github.com/users/smith-m/events{/privacy}","received_events_url":"https://api.github.com/users/smith-m/received_events","type":"User","site_admin":false},"created_at":"2018-09-20T15:39:46Z","updated_at":"2018-09-20T15:39:46Z","author_association":"NONE","body":"@jmcarp\r\n\r\nJIRA marked this issue (Also Airflow-3036? GCP CloudSQL/mysql configuration issues with 1.10) as complete as result of this PR. \r\n\r\nhttps://issues.apache.org/jira/plugins/servlet#issue/AIRFLOW-3036\r\n\r\nDoes this PR address that issue? They don't seem to be related"}}
{"actor":{"display_login":"smith-m"}}