make constant loading dynamic - #81947
Conversation
572ad93 to
32da996
Compare
|
This somehow makes the |
Well, since this can dynamically create a constant post fork, it is a trade off between generating all constants up front even when we don't need most and recreating a constant we use a lot but only post fork. These constants are basically module level variables we inject. I can see how that can create issues, specially since |
4043386 to
47fe713
Compare
47fe713 to
e0247c0
Compare
|
@webknjaz possibly, in my tests the startup is faster, since it only loads what it needs, but if you end up needing most settings it is slower in the end, why i added a forced dump method for ansible-config which is basically how it works before the patch. I'll check the stdin test to see what is going on. |
c257902 to
9f8ffd3
Compare
|
/azp run |
|
Pipelines were unable to run due to time out waiting for the pull request to finish merging. |
|
/azp run |
|
Pipelines were unable to run due to time out waiting for the pull request to finish merging. |
9f8ffd3 to
578766d
Compare
|
@bcoca another |
now constants get populated 'on demand' and cached once set We do need to ensure we initalize deps (constants use in templating for other constants)
deprecations for setting sources only appear when settings is used
Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
578766d to
47371a8
Compare
Don't load a configuration unless we need it.
Config deprecations/warnings less noisy as they will only trigger for config sources if setting is consumed
ISSUE TYPE