Skip to content
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.

Sign up for GitHub

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

Jump to bottom

LaunchDarkly: support shared key for anonymous users #569

Closed
chandlervdw opened this issue Jul 18, 2022 · 1 comment
Closed

LaunchDarkly: support shared key for anonymous users #569

chandlervdw opened this issue Jul 18, 2022 · 1 comment
Assignees
@chandlervdw
Labels
bug Something isn't working wip

Comments

@chandlervdw
Copy link
Member

chandlervdw commented Jul 18, 2022 •
edited
Loading

Issue

The LaunchDarkly integration forcefully repurposes the autogenerated Rudderstack ID for the key that the LaunchDarkly API accepts. This forces you to pass and set a unique ID for every LaunchDarkly user, potentially maxing out your LaunchDarkly plan very quickly.

Solution

From the LaunchDarkly Docs

You do not always need to uniquely identify your anonymous users. Instead, you can use a shared key.

This integration should support options.integrations.LaunchDarkly.key as an override OR it should support an anonymousUsersSharedKey field.
@chandlervdw chandlervdw added bug Something isn't working wip labels Jul 18, 2022
@chandlervdw chandlervdw self-assigned this Jul 18, 2022
This was referenced Jul 18, 2022
Closed
Merged
@saikumarrs
Copy link
Member

It has been fixed in #575.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chandlervdw chandlervdw

Labels
bug Something isn't working wip
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Support LaunchDarkly key override rudderlabs/rudder-sdk-js
2 participants
@chandlervdw @saikumarrs