Story #6134: [EPIC] Pulp import/export
export needs to validate and persist passed-in params
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.
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.
#1 Updated by daviddavis 5 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:
Please register to edit this issue