-
Notifications
You must be signed in to change notification settings - Fork 325
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
More federation-aware API endpoints in brig #1446
Conversation
federation-not-enabled now gives 400
`lookupProfile` is now making one federated request for every non-local domain in the input list of qualified user ids. The logic that partitions the list by domain has been moved away from the Federation module into the corresponding API module (`Brig.API.User`).
05c1bbf
to
373a942
Compare
Also add a test for the `/list-user` endpoint.
0007ed6
to
05400d6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! See minor inline nitpicks.
I suppose that some of the changes we touched upon in discussions (such as moving federation API in brig to make use of more post requests and extensible types rather than lists) is a refactoring planned for a future PR?
Yes, I think it's better to do that on top of #1445. |
Add federation API endpoints:
Hook qualified public API to federator
Tests
TODOs
make(TBD in another PR)/list-users
return an object