delta/openstack/python-openstackclient.git/doc/source/command-objects/role.rst, branch 3.10.0 opendev.org: openstack/python-openstackclient change os in command example to openstack(2) 2016-12-20T01:18:55+00:00 Kevin_Zheng zhengzhenyu@huawei.com 2016-12-20T01:18:55+00:00 847da51deaffcbb4e0f1c3825e60d8181b31b120 In the current doc, the command examples are like "os server create" but the acutal command should be started with "openstack" instead of "os", it is misleading to first time users. Change-Id: I80c96f0938cec382f2f714a500138bd5a2c81aa0 
In the current doc, the command examples are like
"os server create" but the acutal command should
be started with "openstack" instead of "os", it
is misleading to first time users.

Change-Id: I80c96f0938cec382f2f714a500138bd5a2c81aa0
Add support for domain specific roles 2016-08-10T20:32:55+00:00 Henry Nash henryn@linux.vnet.ibm.com 2016-02-23T11:42:40+00:00 5eb7e626b18b033f97f3cf10f2791529f9d75789 A role entity can now be specified as domain specific. Closes-bug: #1606105 Change-Id: I564cf3da1d61f5bfcf85be591480d2f5c8d694a0 
A role entity can now be specified as domain specific.

Closes-bug: #1606105
Change-Id: I564cf3da1d61f5bfcf85be591480d2f5c8d694a0
Add assignment list to v2 identity and deprecate alternate listing 2016-07-22T21:46:29+00:00 Henry Nash henryn@linux.vnet.ibm.com 2016-04-29T22:59:27+00:00 713d92df4e53f74698a1ff2dfcb7514ff22f023b The current identity role list command (both v2 and v3) is overloaded with listing roles as well as assignments (if you provide user, group, project or domain options). This is in addition to the v3 assignment list command designed for this purpose. This overloading complicates the fact that roles can now be domain specific (i.e. have a domain attribute), so the command 'role list --domain <domain-name' will soon become ambigious (this is in a follow on patch). This patch: - Adds a v2 assignments list, with support for pulling the user and project from the auth credentials - For comapability, adds the same auth support to the existing v3 assignments list - Deprecates the use of role list and user role list to list assignments Change-Id: I65bafdef4f8c89e863dab101369d0d629fa818b8 Partial-Bug: 1605774 
The current identity role list command (both v2 and v3) is
overloaded with listing roles as well as assignments (if you
provide user, group, project or domain options). This is in
addition to the v3 assignment list command designed for this
purpose.

This overloading complicates the fact that roles can now be
domain specific (i.e. have a domain attribute), so the
command 'role list --domain <domain-name' will soon become
ambigious (this is in a follow on patch).

This patch:

- Adds a v2 assignments list, with support for pulling the
user and project from the auth credentials
- For comapability, adds the same auth support to the
existing v3 assignments list
- Deprecates the use of role list and user role list to list
assignments

Change-Id: I65bafdef4f8c89e863dab101369d0d629fa818b8
Partial-Bug: 1605774
Remove backticks from help in role commands 2015-09-19T04:40:21+00:00 Hidekazu Nakamura hid-nakamura@vf.jp.nec.com 2015-09-16T15:29:53+00:00 3f532a2b69aa8d98e2fbf58c7f8c9f6aedbd0656 the docs and code had inconsistencies with how it references other arguments, lets just remove the backticks from around them. Change-Id: I43d17b07364e45387c6b9d86c2aca26eeea8ed93 
the docs and code had inconsistencies with how it
references other arguments, lets just remove the
backticks from around them.

Change-Id: I43d17b07364e45387c6b9d86c2aca26eeea8ed93
Add --inherited to the role docs 2015-08-07T17:03:00+00:00 Steve Martinelli stevemar@ca.ibm.com 2015-08-07T05:15:42+00:00 51ae8c78b913a72826f8409e84155148986b7b09 commit Id72670be8640e5c6e2490a6ef849e9ec3493b1a9 forgot to update the docs for role.rst. Change-Id: I97c426ea9b290fc266b34cb0bf97de56cfd098de 
commit Id72670be8640e5c6e2490a6ef849e9ec3493b1a9 forgot to update
the docs for role.rst.

Change-Id: I97c426ea9b290fc266b34cb0bf97de56cfd098de
Minor identity documentation change 2015-07-19T12:06:19+00:00 TerryHowe terrylhowe@gmail.com 2015-07-19T12:06:19+00:00 88c39ef48e2296590ed9dbf532f059ca06655b9e Change-Id: Ib139f2376e70ebb7b5621cdad4da61c64c1f9246 
Change-Id: Ib139f2376e70ebb7b5621cdad4da61c64c1f9246
Add details to the documentation. 2015-07-18T12:56:39+00:00 heha zhanghanqun@unitedstack.com 2015-07-18T10:19:01+00:00 8bae13835495e078be13b91ecc0d688037e91572 Add "or-show" to "project create" and "role create" in the documentation. Closes-Bug: #1475485 Change-Id: I2d98766c4ddd8b2022012c4f6c5e1d4fcebfc42a 
Add "or-show" to "project create" and "role create" in the documentation.

Closes-Bug: #1475485
Change-Id: I2d98766c4ddd8b2022012c4f6c5e1d4fcebfc42a
Enable specifying domain for group and role commands 2015-06-08T14:05:10+00:00 Juan Antonio Osorio Robles juan.osorio.robles@ericsson.com 2015-06-08T13:30:06+00:00 f7feef7f8d1df7b6a28eb6d2e684bf8f1853d356 Many of the commands for the group and role resources were lacking an option to specify the specific domain groups, projects or users belong to. This commit fixes that. Change-Id: I461d2bcfd01ad2dea970de38ec7ad6f4a631ceb1 Closes-bug: #1446546 
Many of the commands for the group and role resources were lacking an
option to specify the specific domain groups, projects or users belong
to. This commit fixes that.

Change-Id: I461d2bcfd01ad2dea970de38ec7ad6f4a631ceb1
Closes-bug: #1446546
add domain scope arguments to v3 role add in doc 2015-05-30T13:30:10+00:00 Guojian Shao guojian@unitedstack.com 2015-05-30T13:18:42+00:00 d14316a8322e58d6ff208ffd6fabdb4890b412f8 There are optional domain scope arguments --user-domain, --group-domain and --project-domain to filter user, group and project for command 'os role add', however, the doc is missing them. Closes-Bug: #1460296 Change-Id: Ie7c7707d183da042c51e98b6cd4003c89efc4032 
There are optional domain scope arguments --user-domain,
--group-domain and --project-domain to filter user, group
and project for command 'os role add', however, the doc
is missing them.

Closes-Bug: #1460296
Change-Id: Ie7c7707d183da042c51e98b6cd4003c89efc4032
Enable specifing domains in "role add" 2015-05-12T08:48:01+00:00 Juan Antonio Osorio Robles juan.osorio.robles@ericsson.com 2015-05-06T19:46:32+00:00 3ca96ef93cda1a3f186febc0e241e2d4adb682eb If users, projects or groups are provided by name, there is a possibility of the existence other users/projects/groups with the same name in other domain. Even though this is not a problem if the actual ID is given instead of a name; this is mostly a usability enhancement. So, three options were added, one for specifying the domain where the user belongs, another one to specify the project's domain, and finally one to specify the group's domain. Change-Id: Iab04b0e04fa75ea5aa3723b8ea42a45f58a6cdb2 Closes-Bug: #1421328 
If users, projects or groups are provided by name, there is a
possibility of the existence other users/projects/groups with the same
name in other domain.  Even though this is not a problem if the actual
ID is given instead of a name; this is mostly a usability enhancement.

So, three options were added, one for specifying the domain where the
user belongs, another one to specify the project's domain, and finally
one to specify the group's domain.

Change-Id: Iab04b0e04fa75ea5aa3723b8ea42a45f58a6cdb2
Closes-Bug: #1421328