Red Hat Bugzilla – Bug 1418338
inconsistency in actions available for resource when accessed through different collections
Last modified: 2018-03-01 08:09:24 EST
Description of problem: When provision, service and automation requests are accessed through /api/requests/:id, the "edit" action is available. When the same resource is accessed through /api/{provision,service,automation}_requests/:id, the "edit" action is not available. The "edit" action should be available regardless to what collection the resource is accessed through. Version-Release number of selected component (if applicable): 5.7.1.0 How reproducible: 100% Steps to Reproduce: 1. create provision, service and automation request 2. access each request through /api/requests and through /api/{provision,service,automation}_requests Actual results: The "edit" action is present only when the request is accessed through /api/requests/:id Expected results: The "edit" action is present also when the request is accessed through /api/{provision,service,automation}_requests/:id
PR: https://github.com/ManageIQ/manageiq/pull/14681
Verified that when provision, service and automation requests are accessed through /api/requests/:id, the "edit" action is available.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:0380