| Summary: | inconsistency in actions available for resource when accessed through different collections | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Martin Kourim <mkourim> |
| Component: | API | Assignee: | Tim Wade <twade> |
| Status: | CLOSED ERRATA | QA Contact: | Martin Kourim <mkourim> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.7.0 | CC: | cpelland, dajohnso, jhardy, jtullo, obarenbo, simaishi, twade |
| Target Milestone: | GA | ||
| Target Release: | 5.9.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | api:rest | ||
| Fixed In Version: | 5.9.0.1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-03-01 13:09:24 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
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 |
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