SamWheating commented on issue #18582: URL: https://github.com/apache/airflow/issues/18582#issuecomment-931459195
I like this idea, but I'm not sure how it would work as Pools are read _and updated_ by the Airflow scheduler, whereas configuration, connections and variables from environment variables are read-only. Maybe we could have something on scheduler start-up which checks for `AIRFLOW__POOL_*` environment variables and creates / updates pool sizes accordingly? I'd be happy to work on this, but I think I need to understand the requirements better first. Could you expand on which aspects of pool configuration you want to manage via environment variables? -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
