Issue #7347
OpenAPI specs: reserved_resources_record missing from TaskResponse
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
API Bindings
Sprint:
Sprint 80
Quarter:
Description
In pulpcore-3.6.0
, OpenAPI specs no longer advertise reserved_resources_record
field in TaskResponse
, and subsequently the field is no longer available in pulpcore-client
bindings (for 3.6.0). The actual REST API response does contain that field.
Please ensure the field is available in the client bindings again, as it is vital to some Pulp applications (RHUI).
Related issues
Associated revisions
Revision c380784c
View on GitHub
OpenAPI: do not discard components without properties
History
#5
Updated by Anonymous 8 months ago
- Status changed from POST to MODIFIED
Applied in changeset pulpcore|2482345527dd14195f9b9839a97f1e16bca60e74.
#7
Updated by dkliban@redhat.com 7 months ago
- Sprint/Milestone set to 3.6.1
#9
Updated by fao89 7 months ago
- Related to Issue #7543: "reserved_resources_record" missing from tasks (python client) added
#10
Updated by dkliban@redhat.com 7 months ago
- Has duplicate Issue #7543: "reserved_resources_record" missing from tasks (python client) added
#11
Updated by dkliban@redhat.com 7 months ago
- Related to deleted (Issue #7543: "reserved_resources_record" missing from tasks (python client))
Please register to edit this issue
OpenAPI: do not discard components without properties
https://pulp.plan.io/issues/7347 closes #7347