[Pulp-dev] problems with publishers in Pulp 3

Dennis Kliban dkliban at redhat.com
Mon Apr 8 11:41:56 UTC 2019


TLDR:

Auto-distribution of publications is performed implicitly instead of
explicitly.
Plugins that don't generate metadata during publish have to provide a
generic publisher.
Users have to keep track of publishers to make sure auto-distribution of
new publications works.

More background:

Publishers in Pulp 3 serve three distinct functions:
  - store configuration for how a publication should be created
  - create publications using the configuration
  - update any distributions that are supposed to be auto updated with new
publications of a repository (auto distribution).

Ansible, Docker, and Maven plugins do not generate any metadata when
creating a publication. So their publishers don't need to store any
configuration. Users of these plugins only get two benefits from publishers:
  - create publications using the configuration
  - update any distributions that are supposed to be auto updated with new
publications of a repository (auto distribution).

The publications created by the publishers of these plugins could be
created using a single generic publish task. So the only remaining benefit
of a publisher for these plugins is the auto-distiribution that occurs when
a Distribution has a repository and a pubisher configured. The only way
this feature is documented right now is with the help text on the
'repository' and 'publisher' fields of Distributions.

Does anyone else see these as problems with the Publishers?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20190408/c9fdf9cd/attachment.htm>


More information about the Pulp-dev mailing list