As a Developer I want to set feature flags so that I can gradually test changes

[olafwrieden]

Given App Configuration Service's feature controls do not support feature management via the NPM package, we may have to pivot to Optimizely - free

• Set up a new Azure App Configuration Service (+ include in deploy scripts)
• Understand how targeting specific users works with React.js - docs only show .NET
• Build useFeatureFlag() and useConfiguration() hooks in React.js

[olafwrieden]

Hey @DanielLarsenNZ I've built a cool custom React Hook that gets a feature flag or configuration from Azure App Configuration Service using the @azure/app-configuration NPM library. It works nicely!

Now, I also want to be able to add user/group-based flags so that a feature becomes visible to a select group of users.
ie. To test the new i18n app languages, tournament admin page, etc.
Plus, a developer flag that permits only our team to the /developer route.

Azure Docs and the JS library don't support this dynamic feature management (staged/targeted rollout). After a day of Googling, the documentation only shows how to do this in a .NET app - not for JavaScript, and no JS client library is available for this either.

Is there a way to get this working in JS, or should I be looking at another feature management provider with a usable JS library to handle this? Would love to learn how we can work with feature flags to gradually release pages/features as we build them rather than using a branch and waiting for a whole page to be built before merging and deploying.