-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
[Proposal] New admin API Routes #4387
Comments
@SD1998 You are welcome. You can find codes about |
@lunny One doubt, so the admin should be able to fetch only the public memberships or both public and private? Thanks. |
The |
Heya! Have you considered using the Sudo API feature to get this information? That way you can do this in Gitea 1.6.0 without waiting for these new APIs. A lot of deficiencies with the API can simply be workarounded using Sudo. |
close this, as zeripath pointed to sudo option ... If a specific api is needed, just as for that specific in a new issue |
In order to delete a user via the API, he mustn't be part of any organisation. Right now it's not possible to get all orgs of an user. I propose a new Route
GET /api/v1/admin/users/:username/orgs
. The route already exists, but without the admin, so it only returns public memberships. I think, as admin you should be able to see those.Another solution would be a listing of all orgs (
GET /api/v1/admin/orgs
). The user then could be tested for org membership for all orgs.A third route which is missing for me is
GET /api/v1/admin/users
, which would be essential for user syncing.The text was updated successfully, but these errors were encountered: