Re: [Pulp-dev] Pulp3 CLI Proof of Concept

Please try out the POC and send all feedback about the implementation or any additional use cases before July 2nd. There are a lot of details on the issue[0] in pulp.plan.io. [0] https://pulp.plan.io/issues/3756 On Mon, Jun 11, 2018 at 1:20 PM, Bihan Zhang wrote: > After gathering some

Re: [Pulp-dev] Ideas for the plugin template

+1 On Mon, Jun 18, 2018 at 3:14 PM, Dana Walker wrote: > +1 > > (Already said it during review, but figured I'd make it official here.) > > Dana Walker > > Associate Software Engineer > > Red Hat > > > > > On Mon, Jun 18, 2018 at 2:01 PM, Daniel

Re: [Pulp-dev] 'id' versus 'pulp_id' on Content

That is a great reason to not use the underscore prefix also for that. We've never formally called this out (that I know of) so that is useful. A good prefix is tough to come up with. Part of the issue is that changing MasterModel affects all models so a prefix like 'pulp_id' would affect all

Re: [Pulp-dev] Ideas for the plugin template

+1 (Already said it during review, but figured I'd make it official here.) Dana Walker Associate Software Engineer Red Hat On Mon, Jun 18, 2018 at 2:01 PM, Daniel Alley wrote: > +1 > > On Mon, Jun 18, 2018 at 12:16 PM, Brian Bouterse > wrote:

[Pulp-dev] Pulp 2 plugin release plan

Earlier today a few of us met to discuss how we can release new Y releases of plugins without a Y release of the platform accompanying them. The initial proposal was to publish a new Y release of a plugin at the same time as a Z release of platform and other plugins. More concretely, we were

Re: [Pulp-dev] 'id' versus 'pulp_id' on Content

I'm -1 on going the underscore idea, partly because of the aforementioned confusion issue, but also partly because but I've noticed that in our API, the "underscore" basically has a semantic meeting of "href, [which is] generated on the fly, not stored in the db". Specifically: - '_href' -

Re: [Pulp-dev] 'id' versus 'pulp_id' on Content

Having a user focus made me realize that it would be useful if a user could easily tell which attributes were common to all content units versus just that one content unit. When scripting for instance that is really useful to know. We could document the 5 attributes that platform provides, but

Re: [Pulp-dev] Ideas for the plugin template

+1 On Mon, Jun 18, 2018 at 12:16 PM, Brian Bouterse wrote: > +1 > > On Mon, Jun 18, 2018 at 8:47 AM, Ina Panova wrote: > >> +1 >> >> >> >> >> Regards, >> >> Ina Panova >> Software Engineer| Pulp| Red Hat Inc. >> >> "Do not go where the path may lead, >> go instead where there is no

Re: [Pulp-dev] Integrating Katello with Pulp3 Recap

Some of the Pulp devs involved in the gap analysis put together this roundup of the gap problem statements [0]. I've scheduled two calls so that we can go over the problem statements to ensure a shared understanding, and think of some possible resolutions. My intention for the calls is to generate

Re: [Pulp-dev] Ideas for the plugin template

+1 On Mon, Jun 18, 2018 at 8:47 AM, Ina Panova wrote: > +1 > > > > > Regards, > > Ina Panova > Software Engineer| Pulp| Red Hat Inc. > > "Do not go where the path may lead, > go instead where there is no path and leave a trail." > > On Thu, Jun 14, 2018 at 10:19 PM, Bihan Zhang

Re: [Pulp-dev] 'id' versus 'pulp_id' on Content

uuid sounds like good compromise. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Thu, Jun 14, 2018 at 9:38 PM, Jeff Ortel wrote: > > > On 06/14/2018 12:19 PM, Jeff Ortel wrote: