Kinde
Join the DiscordJoin the Slack

Welcome to the Kinde community.

P
K
A
A
A
Join

Weird limitation with feature flags in dev and staging environments

RRaymond Barkhouse

We got bit (again) by the weird limitation that feature flags are either env or user overridden. When releasing features a standard process is to:

  • override in a dev or staging environment for a small set of users, test
  • do similar with some production cohort
  • <i>override entire development/staging environment for soak/other testing</i>
  • propage to production

The problem is that feature flags are either env or user, there's no hierarchy of org > env > user (least to most specific).

Also as developers set feature flag defaults it's easy to be in an environment and think you're only effecting it (there is some small text to indicate it is a global change).

What is the suggested approach to rolling out an environmental default while still allowing user overrides?

P
2 comments
PPlain

Thanks for explaining your use case in detail. I will chat with the on what is the best way forward for you.

PPlain

Raymond, we don't have the functionality to do. A workaround would be to have 2 different feature flags and manage the overriding logic in your app. i.e. if user flag is available, use that first -> if not, defer to env then to org

Add a reply
Sign up and join the conversation on Slack
Join