Jabbar Fagan on 26 Jul 2023 23:09:42
May we have the ability to turn functionality on and off at runtime without deploying new code?
Adding a second structure to Microsoft Fabric's deployment pipeline that includes feature flagging may help, but it is probably inappropriate for me to start "solutioning".
The current pipeline structure has 3 stages: dev, test, and prod.
Most of the time we should not need to hop from one environment to the next and back for the majority of change requests.
Help us split code deployment from feature releases. It will simplify and speed up our SDLC.
Imagine preventing or eliminating old git branches that lead to nowhere... assuming Fabric will automatically delete old code and tests from the repository once a feature is fully enabled.
I like how Microsoft can enable or disable features of Windows 11 for subgroups and mitigate poor performance by turning features off before the blast radius gets too big.
Deploying to prod in the dark is very beneficial.
We would like the opportunity to do the same in Fabric.
The current pipeline structure is like a sledgehammer.
Sometimes, just a scalpel will do.
Feature flagging can be that scalpel.
Hopefully, there is no need to reinvent the wheel: