Project

Profile

Help

Issue #9314

closed

RBAC content guard assign/remove endpoints return 200 instead of 201

Added by gerrod over 1 year ago. Updated about 1 year ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
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:
Sprint:
Sprint 104
Quarter:

Description

POST endpoints usually return 201 and the auto-generated schema also thinks these endpoints should return 201. https://docs.pulpproject.org/pulpcore/restapi.html#operation/contentguards_core_rbac_assign_permission

Actions #1

Updated by pulpbot over 1 year ago

  • Status changed from NEW to POST
Actions #2

Updated by dkliban@redhat.com over 1 year ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 104

Added by gerrod over 1 year ago

Revision dc8c2357

Return 201 for RBAC content guard assign/remove endpoints

fixes: #9314

Actions #3

Updated by gerrod over 1 year ago

  • Status changed from POST to MODIFIED
Actions #4

Updated by pulpbot about 1 year ago

  • Sprint/Milestone set to 3.16.0
Actions #5

Updated by pulpbot about 1 year ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF