You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building a new feature and considering rolling it out to a large customer base in phases, there is requirement that certain customers who opt out any new features should be excluded permanently. The opt-out setting is usually stored in another config service which offers RESTful or GraphQL api access. There are other scenarios where we need to call services to get additional context data. Would it make sense to support this feature in flagd? @toddbaert
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When building a new feature and considering rolling it out to a large customer base in phases, there is requirement that certain customers who opt out any new features should be excluded permanently. The opt-out setting is usually stored in another config service which offers RESTful or GraphQL api access. There are other scenarios where we need to call services to get additional context data. Would it make sense to support this feature in flagd? @toddbaert
Beta Was this translation helpful? Give feedback.
All reactions