Project

Profile

Help

Story #6329

Story #6134: [EPIC] Importers/Exporters

As a user, I can create/read/update/delete PulpImporters

Added by daviddavis 23 days ago. Updated 3 days ago.

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

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

History

#1 Updated by daviddavis 9 days ago

Looking at the import API in the design document[0], it looks like there's just a resource PulpImporter that's available at /pulp/api/v3/pulp_importers/. I wonder if we should make importers master/detail models though? Mostly to mirror Exporters (eg /pulp/api/v3/exporters/core/pulp/). That said, I can't think of a use case for this since most of the time, plugins import via sync.

[0] https://hackmd.io/HLptudH9R6S4PCmm8nRmmg#Import

#2 Updated by daviddavis 9 days ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to daviddavis

#3 Updated by ggainey 9 days ago

daviddavis wrote:

Looking at the import API in the design document[0], it looks like there's just a resource PulpImporter that's available at /pulp/api/v3/pulp_importers/. I wonder if we should make importers master/detail models though? Mostly to mirror Exporters (eg /pulp/api/v3/exporters/core/pulp/). That said, I can't think of a use case for this since most of the time, plugins import via sync.

[0] https://hackmd.io/HLptudH9R6S4PCmm8nRmmg#Import

The original intent was for import and export to mirror each other (the APIs originally matched), to among other things minimize user confusion. Also, won't MasterDetail give plugin authors an opportunity to customize/tweak the import process where it may be necessary?

#4 Updated by bmbouter 9 days ago

Making importers master detail is probably the better thing to do. sync's are great for one repo, but we could have future use cases that require us to bring in content to a group of repositories with another mechanism. @daviddavis did I understand your question correctly?

#5 Updated by bmbouter 9 days ago

ggainey wrote:

The original intent was for import and export to mirror each other (the APIs originally matched), to among other things minimize user confusion. Also, won't MasterDetail give plugin authors an opportunity to customize/tweak the import process where it may be necessary?

+1 to Master/Detail, but that's not the mechanism plugin writers use to tweak the import/export process for their content and it's associated models.

What Master/Detail allows is for plugin writers to define a whole, new import codepath that they exclusively own with it's own, new URL endpoints.

#6 Updated by daviddavis 7 days ago

We also discussed this at the rpm meeting today and I think support for using Master/Detail was unanimous. I've updated the design doc.

#7 Updated by pulpbot 3 days ago

  • Status changed from ASSIGNED to POST

Please register to edit this issue

Also available in: Atom PDF