Pulp

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

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?

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?

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.

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.