Actions
Issue #7233
closedopenapi v3 schema operation_id is not always unique
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.
Updated by fao89 over 4 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to fao89
Updated by pulpbot over 4 years ago
- Status changed from ASSIGNED to POST
Added by Fabricio Aguiar over 4 years ago
Updated by Anonymous over 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulpcore|fe6e670ec1cbfda7210ce1331c6f6175094d5877.
Updated by pulpbot over 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Making operation_id unique
https://pulp.plan.io/issues/7233 closes #7233