Bug 1166159
| Summary: | [RFE] API v2 - nested routes for each controller | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Bryan Kearney <bkearney> |
| Component: | API | Assignee: | jmagen <jmagen> |
| Status: | CLOSED UPSTREAM | QA Contact: | Elyézer Rezende <erezende> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.4 | CC: | dcleal, erezende, jaudet, jmagen, mmccune, omaciel, sthirugn |
| Target Milestone: | Unspecified | Keywords: | FutureFeature, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://projects.theforeman.org/issues/3492 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-05-11 15:55:59 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Bryan Kearney
2014-11-20 13:42:37 UTC
Created from redmine issue http://projects.theforeman.org/issues/3492 I am pulling down important features from the 1.7 release. You can read more abotu this feature at http://theforeman.org/manuals/1.7/index.html#Releasenotesfor1.7 I believe that QE will be done by the community on this feature. Moving to POST since upstream bug http://projects.theforeman.org/issues/3492 has been closed ------------- Joseph Magen https://github.com/theforeman/foreman/pull/1068 ------------- Joseph Magen Applied in changeset commit:453dc6939f607d8ae0ff4580b5562734c60b19c5. Upstream bug assigned to jmagen What new nested routes are supposed to have been made available? The Foreman 1.7 release notes [1] say this about the subject: > APIv2: Additional nested URLs to filter resources > > New routes (URLs) have been added to APIv2 that show sets of resources that are associated to another, e.g. domains associated with a subnet, or installation media associated to an operating system. More details on these can be found in the API documentation, look for routes such as /operatingsystems/:operatingsystem_id/media. While this description is helpful, it is not clear which API routes now have nested routes available. Does only the `/media` path have nested routes available? Do more paths have nested routes available? Should one nested route be available for each and every optional parameter than can be provided for a given base path, or not? The upstream redmine bug does not provide any clarification. [2] It is not clear what the criteria is for success or failure for this bug. [1] http://theforeman.org/manuals/1.7/index.html#Releasenotesfor1.7 [2] http://projects.theforeman.org/issues/3492 I don't know why the need info was cleared. Adding it back, for more info check comment 8. closing:upstream this bug, not really worth the effort to test this in QE directly. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |