RosterIn opened a new issue #8291: Enforce Connections & Pools URL: https://github.com/apache/airflow/issues/8291 **Description** Airflow allows Polls and Connection yet the integration between them is up to the user. We have 40+ users who upload DAGs. It's impossible to manually enforce that if user choose to use Connection "X_" then he must also use Pool "X_P". We would love a feature where in the Connection you can associate it to a Pool. So whenever the user is specifying this connection in Operator/Hook he must also specify the Pool - Otherwise the Operator will fail! Or even better save the trouble of having the users to manually specify the pool in the Operator - and stack up the tasks in the pool by itself. I'm not asking to change the current behavior of Pools. This can be an extension of the current behavior. Think of it like queues... The user who writing operator doesn't need to specify to which worker queue the tasks will go. Airflow handle it for him. then why not with Connections and Pools? **Related Issues** Moved from https://issues.apache.org/jira/browse/AIRFLOW-4955
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
