GET /role_assignments do not list the effective role_assignments,
this is done via the "effective" query param as described in the
doc.
For listing role assignments, we also have a similar explanation in
the "roles.inc" doc. After giving some thought, I guess the best option
is to leave both entries. This can sound redundant, but both entries give
pertinent explanation to the doc they are part of. For example, in the
"inherit.inc" doc, we have a introduction to the GET /role_assignments
API and explanations about the "effective", "include_subtree" and
"inherit_to" query parameters, which are essentially part of the
inherited roles feature.
Reviewed: https:/ /review. openstack. org/381777 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=24dd02277c8 d4b9515eb83b7de 00c1683259a666
Committed: https:/
Submitter: Jenkins
Branch: master
commit 24dd02277c8d4b9 515eb83b7de00c1 683259a666
Author: Rodrigo Duarte Sousa <email address hidden>
Date: Tue Oct 4 09:42:28 2016 -0300
Minor fix in role_assignments api-ref
GET /role_assignments do not list the effective role_assignments,
this is done via the "effective" query param as described in the
doc.
For listing role assignments, we also have a similar explanation in
the "roles.inc" doc. After giving some thought, I guess the best option
is to leave both entries. This can sound redundant, but both entries give
pertinent explanation to the doc they are part of. For example, in the
"inherit.inc" doc, we have a introduction to the GET /role_assignments
API and explanations about the "effective", "include_subtree" and
"inherit_to" query parameters, which are essentially part of the
inherited roles feature.
Closes-Bug: 1645554
Change-Id: I38fa771295a1e1 f482b10013f922a 0bd0e432f8d