Project

Profile

Help

Issue #6544

Story #6134: [EPIC] Pulp import/export

export needs to validate and persist passed-in params

Added by ggainey 2 months ago. Updated about 1 month ago.

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:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 72

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.

Associated revisions

Revision 783d035d View on GitHub
Added by ggainey about 2 months ago

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

History

#1 Updated by daviddavis 2 months 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

#2 Updated by rchan 2 months ago

  • Sprint changed from Sprint 71 to Sprint 72

#3 Updated by pulpbot about 2 months ago

  • Status changed from ASSIGNED to POST

#4 Updated by ggainey about 2 months ago

  • Status changed from POST to MODIFIED

#5 Updated by dkliban@redhat.com about 1 month ago

  • Sprint/Milestone set to 3.4.0

#6 Updated by dkliban@redhat.com about 1 month ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF