Feature Toggle implementation as a pluggable django app. Supports SimpleToggle, TimeBombToggle ways to manage release of new features that can be easily toggled on / off.
We deploy django-feature-toggles with our Django application in a cloud-native setup on Kubernetes. The toggles are all initialized at application startup using a management command. We don't manually create any of them.
Side note:In fact, we'd prefer to have the Admin user interface if "Feature Toggles" read-only, apart from the possibility to change a toggle value!
As the setup is really tied to the state of our source code, we have added a FEATURE_TOGGLES dict value to the Django settings of our application. We then initialize the toggle based on that:
If that sounds like a valid use case I'd suggest you add a default management command that would initialize the toggles in the database based on such a FEATURE_TOGGLES dictionary in the Django settings. It could be made flexible, so that people that would want to configure environment too might optionally specify that in the dict, in addition.
We deploy django-feature-toggles with our Django application in a cloud-native setup on Kubernetes. The toggles are all initialized at application startup using a management command. We don't manually create any of them.
Side note: In fact, we'd prefer to have the Admin user interface if "Feature Toggles" read-only, apart from the possibility to change a toggle value!
As the setup is really tied to the state of our source code, we have added a
FEATURE_TOGGLES
dict value to the Django settings of our application. We then initialize the toggle based on that:Suggested Change
If that sounds like a valid use case I'd suggest you add a default management command that would initialize the toggles in the database based on such a
FEATURE_TOGGLES
dictionary in the Django settings. It could be made flexible, so that people that would want to configure environment too might optionally specify that in the dict, in addition.