[Pulp-dev] Plugin relationship to tasks

[Jeremy Audet]

> 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 plugins.

Why should I, as a user, explicitly call HTTP API endpoints to make
sure that Pulp's state is valid? That seems very strange. I'd rather
not worry about that. If there's a path forward that lets plugins
enforce correctness, that seems like a far better path forward.