feat: add AdminAPI and deleteUser method #224
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
grdsdev
force-pushed
the
feat/admin-api-delete-user
branch
from
9a0d290 to
c827d5f
Compare
grdsdev
force-pushed
the
feat/admin-api-delete-user
branch
from
c827d5f to
7729c84
Compare
This was referenced Apr 1, 2024
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.
What kind of change does this PR introduce?
Close #192
What is the current behavior?
Missing implementation of Admin APIs
What is the new behavior?
AuthAdminactor that will contain all admin endpointsdeleteUsermethod for deleting a user using theservice_rolekeyAdditional context
service_rolekey should never be exposed on client code, it will be up to the library user to make sureservice_rolekey is safe.