Allow to specify user email created via /user/new #1759
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
This will require db schema changes as well. I can pick up this ticket @scampion We were initially treating user_id as the place you'd put the email. This is good feedback. Can we get on a call? I want to understand how you're using the proxy + this feature https://calendly.com/d/4mp-gd3-k5k/litellm-1-1-onboarding-chat |
|
We already support user_email in the DB @krrishdholakia |
|
Indeed, I test it and it works for me |
|
you're right @ishaan-jaff, seems like we were just missing it in docs. LGTM |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When you synchronize your current org IAM, it's useful to push also the email since it's standardized compare to user_id