Re: [Pulp-dev] Changesets Challenges

Brian, thanks for the proposal! On Fri, Apr 6, 2018 at 4:15 PM, Brian Bouterse wrote: > Several plugins have started using the Changesets including pulp_ansible, > pulp_python, pulp_file, and perhaps others. The Changesets provide several > distinct points of value which are great, but there are

[Pulp-dev] Various MVP micro-discussions

I made some changes to the MVP document. These changes should not be controversial, but some more eyes would be welcome. - Minor obvious fixes: - https://pulp.plan.io/projects/pulp/wiki/Pulp_3_Minimum_Viable_Product/155/diff - Content Management "refactor: - Separate conte

[Pulp-dev] 2.16.1 Dev Freeze -- Tuesday, April 17 at 21:00 UTC

Any Pulp2 core or plugin code that you want included in the 2.16.1 release must be: a) merged to master by 21:00 UTC, April 17th b) associated with a story, refactor, task or a bugfix issue. If you want/need to adjust this date, please reply on list. The release page containing the schedule is he

Re: [Pulp-dev] Various MVP micro-discussions

> > Throughout the MVP there are many references to lazy sync. They have been > changed to red, but IMO we should just remove them. > Are the items we're removing from the MVP being moved to the 3.1+ planning document on the wiki? We don't want to lose track of any of these items. This applies al

Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

Here's another one that needs to be groomed and added to the sprint(thanks kersom!) - (@David maybe?) Content Filters https://pulp.plan.io/issues/3084 All of these have been added to the sprint: - https://pulp.plan.io/issues/3552 - https://pulp.plan.io/issues/3395 - https://pulp.pla

Re: [Pulp-dev] Content paths in Pulp 3

I've updated the issue https://pulp.plan.io/issues/3472 to reflect the current consensus. However, I have some other points I'd like to discuss before we move on. *Implied endpoint:* v3/content/ansible/roles/ implies that there is a v3/content/ansible/. Even though this does not exist, it could,

[Pulp-dev] Pulp 3 REST API Challenges

Folks, Austin, Dennis, and Milan have identified the following issues with current Pulp3 REST API design: - Action endpoints are problematic. - Example POST@/importers//sync/ - They are non-RESTful and would make client code tightly coupled with the server code. - These en

Re: [Pulp-dev] Pulp 3 REST API Challenges

I agree on these issues being sound and worth resolving. I would much prefer we maintain a truly RESTful API if possible. +1 resuming particular solution discussion. --Dana Dana Walker Associate Software Engineer Red Hat On Mon, Apr 9, 2018 at 3: