BasPH commented on issue #18582: URL: https://github.com/apache/airflow/issues/18582#issuecomment-933792473
@fritz-astronomer FWIW pools can also be imported from a json file: https://stackoverflow.com/a/69255203/3066428 IMO if we support configuration via env vars, we should either support everything or nothing, so I'd opt for having pools configurable via env vars since we support env vars for everything else too. @potiuk (thinking out loud) I think there are many ways the user experience around configuration could improve. E.g. connections and variables set via env vars could be listed in the UI and we could periodically sync configuration to e.g. find discrepancies in configuration between instances. Several things in Airflow are already import-able using a json file. I don't have great experience with terraform state, but how about we extend the importing functionality to make all things import-able from one single json file? The config sync could be another API endpoint? -- 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]
