Pulp

Importers can be for more than just syncing repositories. For instance, plugins might want to use an importer for a rich copy, but that importer may not need a feed_url.

This could be solved by validating the presence of the field feed_url before triggering the sync.

ipanova@redhat.com wrote:

This could be solved by validating the presence of the field feed_url before triggering the sync.

That is currently how it is done. https://github.com/pulp/pulp_file/blob/master/pulp_file/app/tasks/synchronizing.py#L52

Since this is no longer a Pulp issue, and is a pulp_file issue, the file plugin has no use for importers that don't have a feed_url, so I am +1 on accepting this.

maybe s/importers/remotes/ but still LGTM

Wait, why was this converted back to a pulp issue from a pulp_file issue? This isn't something we're planning to do in core.

A pulp_python issue should still be filed but this should remain a pulp_file issue.

With the change from "importer" to "remote" we were thinking that a remote is nothing without a url.