Feature Request: Separate control over Identity and Environment flags Local/Remote

[deefdragon]

I'm using a large number of Environment flags to dictate api access on a per endpoint basis. For these flags, they change so infrequently that using Local Evaluation makes the most sense to avoid the latency hit.

When doing most of my Identity based checks however, Im checking for specific Identity Overrides, which do not function in Local, so I must use Remote Evaluation.

Currently, it is possible to accomplish this with two clients, but it is obviously undesirable to require duplicating client setup.

This request is to add extra options values for the client of WithRemoteEnvironmentEvaluation(), and WithRemoteIdentityEvaluation(). This allows first setting the default to local with WithLocalEvaluation(ctx) (and setting the context) and then setting which you wish to have Remotely evaluated second.

[dabeeeenster]

Ah interesting! We are working on getting Identity overrides working with local evaluation (Flagsmith/flagsmith#1762) - would this solve your use case? There would be limits to the number of overrides as it affects the size of the environment payload in local eval mode.