Project

Profile

Help

Issue #7233

closed

openapi v3 schema operation_id is not always unique

Added by dkliban@redhat.com over 2 years ago. Updated over 2 years ago.

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

Description

The 'read' and 'delete' operation_id is repeated for all the resources while the 'list' and 'create' operations have unique names such 'pulp_api_v3_repositories_container_container_create' and 'pulp_api_v3_repositories_container_container_list'.

The pattern seems to be that paths that have a name such {artifact_href} have their operation_id repeated. While paths that are in form of /pulp/api/v3/artifacts/ have unique names. Perhaps we should be changing the paths from /pulp/api/v3/artifacts/{pk}/ to {artifact_href} later in the code.

Actions #1

Updated by fao89 over 2 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to fao89
Actions #2

Updated by pulpbot over 2 years ago

  • Status changed from ASSIGNED to POST

Added by Fabricio Aguiar over 2 years ago

Revision fe6e670e

Making operation_id unique

https://pulp.plan.io/issues/7233 closes #7233

Actions #3

Updated by Anonymous over 2 years ago

  • Status changed from POST to MODIFIED
Actions #4

Updated by dkliban@redhat.com over 2 years ago

  • Sprint/Milestone set to 3.6.0
Actions #5

Updated by pulpbot over 2 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF