Actions
Issue #6544
closed
Story #6134: [EPIC] Pulp import/export
export needs to validate and persist passed-in params
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 72
Quarter:
Description
core_export has a column for storing the params used to invoke export, but we don't pay attention to them. Validate incoming params according to the design-doc and make sure they are persisted.
Updated by daviddavis about 4 years ago
I noticed that params on Export as well as some other fields such as sha256 on PulpExport and last_export on PulpExporter should be marked as read_only since they should not be set by users:
https://docs.pulpproject.org/restapi.html#operation/exporters_core_pulp_exports_create
https://docs.pulpproject.org/restapi.html#operation/exporters_core_pulp_create
Updated by pulpbot almost 4 years ago
- Status changed from ASSIGNED to POST
Added by ggainey almost 4 years ago
Updated by ggainey almost 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulpcore|783d035d03929a7ca79349001ff19e37df33a14e.
Updated by dkliban@redhat.com almost 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
Validate and serialize parameters used to invoke Export.
This only implements the infrastructure to validate incoming parameters and store them in the 'params' field, it does not implement the functions (full/incremental, dry-run, export-by-version) being requested.
closes #6544