| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
Adding the possibility to create projects hierarchies by adding
the parent field in the create project call.
Co-Authored-By: Victor Silva <victor@lsd.ufcg.edu.br>
Implements: bp hierarchical-multitenancy
Change-Id: I4eac4f5bc067634cc38c305dacc59ab1da63c153
|
| |
|
|
|
|
|
|
|
| |
Keystone Server already surfaces an error for this operation, but
we should restrict the user, and not offer --domain to be changed
for a project.
Change-Id: I48317e8accfea3c285e6ad213e75b783de8070ac
Closes-Bug: #1418384
|
| |
|
|
|
|
|
|
|
| |
try and add some consistency with the show and delete commands.
replace 'show x' with 'display x'
change 'delete a y' with just 'delete y'
Change-Id: I47dfa8ee23ac5c41b355796415eb515155832f65
|
| |
|
|
|
|
|
|
|
|
| |
The headers in the doc files are the commands, not a description.
I missed thiese in the original reviews:
https://review.openstack.org/140567
https://review.openstack.org/140581
Change-Id: Iae2631f6b485e8c568ff305e5992c193f80ebe71
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is part2. Add support for these objects:
identity.project(v2.0)
identity.role(v2.0)
identity.user(v2.0)
identity.project(v3)
identity.role(v3)
identity.user(v3)
identity.group(v3)
Closes-Bug: #1400597
Change-Id: I270434d657cf4ddc23c3aba2c704d6ef184b0dbc
|
| |
|
|
|
|
|
| |
Essentially performing GET /users/{user_id}/projects
Change-Id: Iae6ddfc86a856fa24fbe293ec4af52ea671390f8
Closes-Bug: #1394793
|
| |
|
|
|
|
|
|
|
|
| |
Currently, only deleting via IDs is possible for groups, projects
and users.
We should have an optional --domain argument that allows for
a name to be specified for the resource. (Since these are all
namespaced by domains).
Change-Id: I18ace3db85a3969f0b97678d432d6f8368baa9cd
|
|
|
project
role
user
user role
Change-Id: I445e09a3ffb69114912ae562a9285963a636bfd1
|