Project

Profile

Help

Issue #3022

Tasks delete endpoint does not work if the optional parameter was not provided.

Added by kersom about 4 years ago. Updated over 2 years ago.

Status:
CLOSED - WONTFIX
Priority:
Low
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

As per documentation [https://docs.pulpproject.org/dev-guide/integration/rest-api/tasks.html#deleting-completed-tasks\] the state (string) - (optional) only delete tasks currently in this state.
However if the state is not provided the response is always 403. If the state is provided then response can be 204. Basically, an optional parameter is behaving as necessary.

To recreate:

Use HTTP DELETE on the path: /pulp/api/v2/tasks/ without provide the state.

History

#1 Updated by amacdona@redhat.com about 4 years ago

  • Severity changed from 1. Low to 2. Medium
  • Triaged changed from No to Yes

I see 2 potentially separate issues here. 1) we should make `state` non-optional. 2) an invalid request should not return a 403, so that should be investigated as well.

#2 Updated by bmbouter over 2 years ago

  • Status changed from NEW to CLOSED - WONTFIX

#3 Updated by bmbouter over 2 years ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF