[Pulp-dev] Plugin relationship to tasks

Dennis Kliban dkliban at redhat.com
Tue Mar 27 17:06:27 UTC 2018

On Tue, Mar 27, 2018 at 12:23 PM, Austin Macdonald <amacdona at redhat.com>

> After some reflection, I think we have been too focused on the small
> points (plugin complexity, URL organization, actions vs nouns). They should
> be discussed, but we don't have consensus around the primary concern.
> Correctness is what motivated this proposal, so I'd like to take a step
> back and discuss only correctness.
> My assertion:
> Plugins should be able to define and enforce constraints on the content
> membership of a repository.
> My reasoning:
> Some plugins have natural constraints on the membership of a repository.
> Two Docker Tags of the same name cannot be in a the same Repository.
> Manifest Lists cannot be in a repository without the Manifests that are
> listed. It would be fundamentally incorrect to prevent the plugins from
> enforcing these kinds of constraints. I think there are similar problems
> with errata package lists.
The current plugin API allows plugin authors to define custom REST API
endpoints that can perform any custom validation needed for the plugin. The
repository version creation REST API provided by pulpcore only validates
that the content exists. We should document this limitation and recommend
that users use Repository Version creation APIs provided by specific

> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20180327/b92191b9/attachment.htm>

More information about the Pulp-dev mailing list