-
Notifications
You must be signed in to change notification settings - Fork 28
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
Add Group API #98
Add Group API #98
Conversation
Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de>
rpc GetGroup(cs3.identity.group.v1beta1.GetGroupRequest) returns (cs3.identity.group.v1beta1.GetGroupResponse); | ||
// Gets the information about a group based on a specified claim. | ||
rpc GetGroupByClaim(cs3.identity.group.v1beta1.GetGroupByClaimRequest) returns (cs3.identity.group.v1beta1.GetGroupByClaimResponse); | ||
// Gets the groups of a group. |
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.
Gets the members of a group
@@ -45,9 +45,11 @@ message UserId { | |||
message User { | |||
UserId id = 1; | |||
string username = 2; |
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.
Here we can just add the new fields at the end to not limit the breakage.
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.
@butonic go over my comments and then you can just remove the proto.lock file and run protolock init
.
You may need to install the protolock tool.
// Represents a group of the system. | ||
message Group { | ||
GroupId id = 1; | ||
string groupname = 2; |
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.
group_name
Yep, or you can just run |
moved to #99 |
This PR adds a readonly groups api to CS3.
Similar to users groups have a persistent, non reassignable, stable, unique identifier which we call
id
In addition to that the CS3 API knows other identifiers like a name, an email and numeric identifiers (which we used to carry as opaque payload).
I did not care to preserve backwards compatability and reused old ids, which is why there are build failures for protobuf.
Let me know if we can go forward with this or if the API is considered staple and we need to keep backwards compatabililty.