feat(node): add sdk methods for organization apis #4826
Conversation
| list(); | ||
| create(payload: IOrganizationCreatePayload); |
There was a problem hiding this comment.
Why these two methods are public? For me it doesn't make sense - API KEY is attached to single organization, so why we want to allow to cross that boundary?
Whose organizations will be returned? Organizations of the owner?
I'm just wondering - but I implemented that anyway.
| removeMember(memberId: string); | ||
| updateMemberRole( | ||
| memberId: string, | ||
| payload: IOrganizationUpdateMemberRolePayload | ||
| ); |
There was a problem hiding this comment.
These two methods also may cause problems when full Role-based access control will be implemented?
I can imagine member that may bypass role-based access control by using API KEY to remove other members or update their role - they will do it as "organization owner" (assuming that member would be able to see api key).
michaldziuba03
changed the title
|
Thanks for your contribution @michaldziuba03 |
What change does this PR introduce?
This PR introduces new SDK methods for organization API.
Why was this change needed?
Closes #4775
Other information (Screenshots)