documentation needs to be clarified about differences between subtree_as_ids and subtree_as_list
Bug #1506986 reported by
Raildo Mascena de Sousa Filho
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
Fix Released
|
Low
|
Lance Bragstad | ||
Bug Description
The current documentation in the idendity API V3 just explain what is the API returns about subtree_as_ids and subtree_as_list.
The same documentation needs to be add for parents_as_ids and parents_as_list
We need to explain what is the difference in the API response between this two operations and what is the excepted use for it.
| summary: |
documentation needs to be clarified about differences between - subtree_as_ids and subtree_as_list and the same for parents_as_ids and - subtree_aslist + subtree_as_ids and subtree_as_list |
| description: | updated |
| Changed in keystone: | |
| assignee: | nobody → Raildo Mascena de Sousa Filho (raildo) |
| Changed in keystone: | |
| assignee: | Raildo Mascena de Sousa Filho (raildo) → nobody |
| Changed in keystone: | |
| assignee: | nobody → Lance Bragstad (lbragstad) |
| status: | New → In Progress |
| Changed in keystone: | |
| importance: | Undecided → Low |
| tags: | added: documentation |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to keystone-specs (master) | #1 |
| Changed in keystone: | |
| status: | In Progress → Fix Committed |
| Changed in keystone: | |
| milestone: | none → mitaka-1 |
| Changed in keystone: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 17129323aefaf96
Author: Lance Bragstad <email address hidden>
Date: Fri Oct 16 15:10:37 2015 +0000
Improve get project query strings
This commit improves the documentation describing the parents_as_list,
parents_as_ids, subtree_as_list, and subtree_as_ids query strings.
Change-Id: I21b4dcf1c3e3af
Related-Bug: 1506653
Closes-Bug: 1506986