You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/02/15 22:49:35 UTC

[GitHub] [airflow] potiuk commented on pull request #21223: Added Feature: Create Pools from Env Vars.

potiuk commented on pull request #21223:
URL: https://github.com/apache/airflow/pull/21223#issuecomment-1040875658


   Does it mean now that instead of one place (DB) you want to keep state of pools in 3 different places (DB, Env, state file)? 
   And modify scheduler job to sync pool every time scheduler start (why scheduler job, what happens if you have multiple schedulers?). 
   And add a new "sync" command to sync the state of mostly static pools that should be changed VERY RARELY?
   
   All this that can be replaced with running this once when you want to configure pools (which you can re-run every time you want to modify pools): 
   
   ```
   airlfow pools import <pool_file>
   ```
   
   Sorry. But this is hard no.
   
   


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org