Re: [Pulp-dev] Plugin relationship to tasks

> > >- /api/v3/repositories//versions/ endpoint does not perform >plugin specific validation which can lead to "broken" repository versions. >- Plugin authors don't have any convention to follow when creating >custom REST API endpoints for creating repository versions. >- As a

Re: [Pulp-dev] Plugin relationship to tasks

On Tue, Mar 27, 2018 at 1:36 PM, Jeremy Audet wrote: > > 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

Re: [Pulp-dev] Plugin relationship to tasks

On Tue, Mar 27, 2018 at 12:23 PM, Austin Macdonald wrote: > 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

Re: [Pulp-dev] Pulp 2.16.0 RC is blocked

On Mon, 2018-03-26 at 16:56 -0400, Patrick Creech wrote: > Head's up, the upgrade path still needs a little work from celery < 4 to > celery > 4 on rhel. > > I will be working to resolve these issues asap A fix has been vetted by QE, RC is unblocked. Will provide builds asap signature.asc

Re: [Pulp-dev] Plugin relationship to tasks

On Tue, Mar 27, 2018 at 12:00 AM, Brian Bouterse wrote: > I also want to look at how this will affect our user experience. With this > change, I believe plugin tasks are put at the center of the user experience > and the repositories, content, and versions are moved to the

Re: [Pulp-dev] Plugin relationship to tasks

On Tue, Mar 27, 2018 at 12:02 AM, Austin Macdonald wrote: > > > On Mon, Mar 26, 2018 at 4:43 PM, Dennis Kliban wrote: >> >> On Mon, Mar 26, 2018 at 3:38 PM, Austin Macdonald >> wrote: >>> >>> >>> >>> On Mon, Mar 26, 2018 at 2:30 PM,