Issue #6544: export needs to validate and persist passed-in params - Pulp

Actions

Send by e-mail Copy link

Issue #6544

closed

Story #6134: [EPIC] Pulp import/export

export needs to validate and persist passed-in params

Added by ggainey about 3 years ago. Updated about 3 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

ggainey

Category:

Sprint/Milestone:

3.4.0

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version:

Platform Release:

OS:

Triaged:

Yes

Groomed:

Yes

Sprint Candidate:

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.

Actions

Copy link

Updated by daviddavis about 3 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

Actions

Copy link

Updated by rchan about 3 years ago

Sprint changed from Sprint 71 to Sprint 72

Actions

Copy link

Updated by pulpbot about 3 years ago

Status changed from ASSIGNED to POST

PR: https://github.com/pulp/pulpcore/pull/687

Added by ggainey about 3 years ago

Revision 783d035d

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

Actions

Copy link