Actions
Task #8860
closedMove FilesystemExporter out of plugin API into pulpcore
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
Actions
Move FilesystemExporter into core
fixes #8860