-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flag Evaluation Route Returns All Flags #63
Comments
Thanks for bringing this to our attention. The relay endpoint is supposed to behave just like the regular service endpoint, so it should be returning only the client-side flags. So that's a pretty straightforward bug, and we'll have a fix ASAP. |
When I send a GET request to https://app.launchdarkly.com/sdk/evalx/5c98f0804421b90813e75ca5/users/eyJrZXkiOiJVbmtub3duIn0, I get:
which is ONLY our client side flags. When I send a GET request to https://launch-darkly-relay.dndbeyond.com/sdk/evalx/5c98f0804421b90813e75ca5/users/eyJrZXkiOiJVbmtub3duIn0, I get:
which is ALL of our flags. |
This is fixed in version 5.6.0. |
Confirmed!!!!!!!! Now I get:
|
add /meval mobile stream endpoint (pings only)
I recently installed the ld-relay via docker and noticed that
/sdk/evalx/{clientId}/users/{user}
returns all flags instead of only client side flags.Is this expected? When the client connects to https://app.launchdarkly.com, it only returns flags that have been marked as "Make this flag available to client-side SDKs", but when I access that route via the ld-relay, it returns all flags.
Is it possible to only return client side flags?
The text was updated successfully, but these errors were encountered: