Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow Pools to be set via ENV
See original GitHub issueDescription
As a system/airflow admin - I prefer being able to see all the various configurations of my instance, and being able to version and audit them.
Pools are a very important subsystem in Airflow - however they are currently only configurable via the UI and CLI.
I would like to be able to configure Pools via ENV variables, as I am able to with configuration settings, connections, and variables.
Something like AIRFLOW_POOL_DEFAULT_SIZE = 128
Use case/motivation
No response
Related issues
No response
Are you willing to submit a PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project’s Code of Conduct
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:13 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yea @thcidale0808 - I imagine that would fit the needs of the individuals I’ve talked to with this. The ENV does it’s best to ADD or UPDATE pools. Users will be made aware that pools (like connections and variables) can also come from many sources, and if the env disappears, then it’s on the user to remove the pool (which also doesn’t feel like the worst “failure state” to me?)
Yes; I always liked this hot reload functionality of Prometheus: https://prometheus.io/docs/prometheus/latest/configuration/configuration/. +1 for rewriting the configuration, it has other nasty problems e.g. https://github.com/apache/airflow/issues/8255