Bug 1420872 - entities under /api/notifications collection are missing "delete" action with "DELETE" method
Summary: entities under /api/notifications collection are missing "delete" action with...
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: API
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: GA
: 5.9.0
Assignee: Tim Wade
QA Contact: Martin Kourim
Whiteboard: api:rest
Depends On:
TreeView+ depends on / blocked
Reported: 2017-02-09 17:24 UTC by Martin Kourim
Modified: 2018-03-01 13:09 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-03-01 13:09:24 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:0380 0 normal SHIPPED_LIVE Moderate: Red Hat CloudForms security, bug fix, and enhancement update 2018-03-01 18:37:12 UTC

Description Martin Kourim 2017-02-09 17:24:42 UTC
Description of problem:
Entities under /api/notifications collection have "delete" action with "POST" method available, but unlike entities in other collections (e.g. service_dialogs, blueprints, ...) they are missing "delete" action with "DELETE" method.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. create notifications (e.g. with automation request, provosioning requests, ...)
2. check under /api/notifications/:id that there is not "delete" action with "DELETE" method available

Comment 2 Tim Wade 2017-06-27 16:27:02 UTC
PR: https://github.com/ManageIQ/manageiq/pull/14775

Comment 3 Martin Kourim 2017-10-13 13:13:52 UTC
Verified on that resources under /api/notifications collection have "delete" action with "DELETE" method available.

Comment 6 errata-xmlrpc 2018-03-01 13:09:24 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.