-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set feature flag base on setting #15808
Set feature flag base on setting #15808
Conversation
Context: This would address my comments on #15799 |
More context, people have talked this out at some point or another: #15702 would add dynaconf. The key feature of that is getting settings from environment variables. This includes nested variables, like But that's unlikely to be ready very soon, and we want to unblock the work that this would allow. This will still probably change a little bit what that PR is doing so I want to get everyone in the loop and then we can go ahead with this merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @TheRealHaoLiu , this implements this proposal: https://handbook.eng.ansible.com/proposals/0068-Feature-flags-configuration-at-install-time
This topic keeps getting deeper Apparently, the That appears to maybe be when this was added. Merged Apr 19, 2024. Check commit, not in any tags. Waiting for the next major release apparently. @TheRealHaoLiu your PR now actually makes sense. Without this piece of the puzzle, I have to admit this appeared to be nonsense. Why not just set the nested value? It seems we have a long way to go before dynaconf will allow an environment variable to do this. |
46c4bbf
to
d7d7a8e
Compare
|
SUMMARY
Set value of feature flag base on local setting
ISSUE TYPE
COMPONENT NAME
AWX VERSION
ADDITIONAL INFORMATION