App azure configuration provides a mechanism for dynamic configuration [ConfigureRefresh] where configuration can be changed on a fly and the changed value is available to the server. How does this differs from the Feature Flag which seems like to be serving the same purpose , or if there is something extra which it provides us?. Thanks in advance.
Feature flag is different from App Configuration. Latter is the centralized app config managment. Feature flags allows us to turn on/off features via configuration. Changing app configs usually needs restarting the app. but with Azure App Config SDK provides push and pull approach to fetch configs with out restarting it.
Feature flags are really handy if you want to deploy to production frequently, but don't want to hide some features from your users (e.g. maybe they are still in progress)
Have a look Feature Management github repo It has injectable interface, decorators for actions/controllers and also MVC Tag helpers. just works straight out of the box. The Features json can be in the appsettings or in the Azure App Configuration. if its in the App Configuration it has Push and Pull model to fetch updated configs with out restart.
Is there a way to manage Azure Feature Flags through a Rest API?
Can this be used with asp net 4.8?
App azure configuration provides a mechanism for dynamic configuration [ConfigureRefresh] where configuration can be changed on a fly and the changed value is available to the server. How does this differs from the Feature Flag which seems like to be serving the same purpose , or if there is something extra which it provides us?. Thanks in advance.
Feature flag is different from App Configuration. Latter is the centralized app config managment. Feature flags allows us to turn on/off features via configuration. Changing app configs usually needs restarting the app. but with Azure App Config SDK provides push and pull approach to fetch configs with out restarting it.
You can save you app properties in app secret for local development, and in azure for production!!
fun with flags
why the big deal its a bit field
Feature flags are really handy if you want to deploy to production frequently, but don't want to hide some features from your users (e.g. maybe they are still in progress)
Have a look Feature Management github repo It has injectable interface, decorators for actions/controllers and also MVC Tag helpers. just works straight out of the box. The Features json can be in the appsettings or in the Azure App Configuration. if its in the App Configuration it has Push and Pull model to fetch updated configs with out restart.