Actions
Issue #3962
closed
Artifact create response is not documented
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 42
Quarter:
Description
The response is not documented for POST '/pulp/api/v3/artifacts'.
As a result the generated client doesn't know how to interpret the response and simply sets it to None.
Added by dkliban@redhat.com over 6 years ago
Added by dkliban@redhat.com over 6 years ago
Revision 6181cd14 | View on GitHub
Problem: drf_yasg does not generate a response schema for Artifact
Solution: provide a custom view inspector for ArtifactViewset
The custom inspector generates responses for multipart form uploads. As a result the generated OpenAPI 2.0 schema has responses for Artifact GET and POST.
Updated by dkliban@redhat.com over 6 years ago
- Status changed from NEW to POST
Updated by daviddavis over 6 years ago
- Assignee set to dkliban@redhat.com
- Triaged changed from No to Yes
- Sprint set to Sprint 42
Updated by dkliban@redhat.com over 6 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulp|6181cd1423c8d8a9211a078c9c9a3ab31f2d0cb1.
Updated by bmbouter about 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
Problem: drf_yasg does not generate a response schema for Artifact
Solution: provide a custom view inspector for ArtifactViewset
The custom inspector generates responses for multipart form uploads. As a result the generated OpenAPI 2.0 schema has responses for Artifact GET and POST.
closes: #3962 https://pulp.plan.io/issues/3962