We have a process where feature flags are updated prior to code that uses them being deployed.
We were hoping that we could archive flags that aren't being used anymore but, that those flags would still evaluate under "stringVariation" while the new code doesn't use those flags is being deployed.
However, when we attempt to check the value of an archived flag with "stringVariation" we get back the default value instead of the archived value.
Is it possible to add an option to include archived flags when checking stringVariation? Or do you have any ideas of a workaround?
We have a process where feature flags are updated prior to code that uses them being deployed.
We were hoping that we could archive flags that aren't being used anymore but, that those flags would still evaluate under "stringVariation" while the new code doesn't use those flags is being deployed.
However, when we attempt to check the value of an archived flag with "stringVariation" we get back the default value instead of the archived value.
Is it possible to add an option to include archived flags when checking stringVariation? Or do you have any ideas of a workaround?