Project

Profile

Help

Task #8860

closed

Move FilesystemExporter out of plugin API into pulpcore

Added by daviddavis over 3 years ago. Updated about 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 102
Quarter:

Description

FilesystemExporter suffers the same problem as Distributions once did.

The inheritance looks like this:

Exporter -> FilesystemExporter -> FileFilesystemExporter

Where Exporter is the Master class and FileFilesystemExporter is the Detail class. FilesystemExporter is in pulpcore holds the code for exporting artifacts to the filesystem while the Detail class (e.g. FileFilesystemExporter) determines what artifacts to export. For example, for plugins with publications, this would be published artifacts but for plugins without publications, this would be the artifacts for a repository version's content.

It's worth noting that the FilesystemExporter is in tech preview and only used by pulp_file.


Related issues

Related to File Support - Task #8861: Remove filesystem exporterCLOSED - CURRENTRELEASEdaviddavis

Actions
Blocks Pulp - Issue #8695: FileSystemExporter cannot cross os boundaryCLOSED - CURRENTRELEASEdaviddavisActions
Blocked by Pulp - Issue #8868: Bindings don't properly namespace APICLOSED - CURRENTRELEASEdkliban@redhat.comActions

Also available in: Atom PDF