-
Notifications
You must be signed in to change notification settings - Fork 73
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
[Feature]: API client can assign a space role to a user with POST /v3/roles
#160
Comments
cf set-space-role
POST /v3/roles
mnitchev
added a commit
that referenced
this issue
Nov 4, 2021
* Currently supports only creating space roles * Generate predictable role binding names by doing a sha256sum on the role name and user. The name is also prefixed with `cf-` to ensure it starts witha lowercase letter. * The role will fail to create if the user does not have a role in the parent org namespace (as per the docs for POST /v3/roles) Issue: #160 Co-authored-by: Mario Nitchev <[email protected]> Co-authored-by: Kieron Browne <[email protected]>
danail-branekov
added a commit
that referenced
this issue
Nov 5, 2021
* Currently supports only creating space roles * Generate predictable role binding names by doing a sha256sum on the role name and user. The name is also prefixed with `cf-` to ensure it starts witha lowercase letter. * The role will fail to create if the user does not have a role in the parent org namespace (as per the docs for POST /v3/roles) Issue: #160 Co-authored-by: Mario Nitchev <[email protected]> Co-authored-by: Kieron Browne <[email protected]>
danail-branekov
added a commit
that referenced
this issue
Nov 5, 2021
* Currently supports only creating space roles * Generate predictable role binding names by doing a sha256sum on the role name and user. The name is also prefixed with `cf-` to ensure it starts witha lowercase letter. * The role will fail to create if the user does not have a role in the parent org namespace (as per the docs for POST /v3/roles) Issue: #160 Co-authored-by: Mario Nitchev <[email protected]> Co-authored-by: Kieron Browne <[email protected]>
kieron-dev
pushed a commit
that referenced
this issue
Nov 9, 2021
* Currently supports only creating space roles * Generate predictable role binding names by doing a sha256sum on the role name and user. The name is also prefixed with `cf-` to ensure it starts witha lowercase letter. * The role will fail to create if the user does not have a role in the parent org namespace (as per the docs for POST /v3/roles) Issue: #160 Co-authored-by: Mario Nitchev <[email protected]> Co-authored-by: Kieron Browne <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
As an admin
I want to assign space roles to users
So that I can control permissions in the space
Acceptance Criteria
GIVEN a space exists
AND a user other than the admin exists
AND a
ClusterRole
existsWHEN I make the following request:
THEN I get the following response:
AND I see a
RoleBinding
in the space namespace for the specified userDev Notes
POST /v3/roles
The text was updated successfully, but these errors were encountered: