potiuk commented on issue #18582: URL: https://github.com/apache/airflow/issues/18582#issuecomment-934635333
> @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? Sounds like a good idea, especially that it might actually open up possibility for something much more interesting (not sure if we want that) - namely reloading configuration provided outside of the DB without restarting Airflow. It would not be possible for all parameters, but I think that might be a good opportunity to refactor the "conf" part and make it truly independent from other parts of Airflow. Right now we have those nasty loops `conf -> models -> settings -> conf` which are creating all kinds of problems (for example cyclic imports when initializing secret backends). I'd very much support rewriting this part. -- 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]
