[Pulp-dev] Pulp 3 REST API Challenges
dawalker at redhat.com
Mon Apr 9 20:16:38 UTC 2018
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
Associate Software Engineer
On Mon, Apr 9, 2018 at 3:18 PM, Austin Macdonald <austin at redhat.com> wrote:
> Austin, Dennis, and Milan have identified the following issues with
> current Pulp3 REST API design:
> - Action endpoints are problematic.
> - Example POST@/importers/<plugin>/sync/
> - They are non-RESTful and would make client code tightly coupled
> with the server code.
> - These endpoints are inconsistent with the other parts of the REST
> - DRF is not being used as intended for action endpoints so we have
> to implement extra code. (against the grain)
> - We don't have a convention for where plug-in-specific, custom
> repository version creation endpoints.
> - example POST@/api/v3/<where?>/docker/add/
> - needs to be discoverable through the schema
> - For direct repository version creation, plugins are not involved.
> - validation correctness problem: https://pulp.plan.io/issues/3541
> - example: POST@/api/v3/repositories/<repository_id>/versions/
> We would like to get feedback on these issues being sound and worth
> resolving before we resume particular solution discussion.
> Austin, Dennis, and Milan
>  https://www.redhat.com/archives/pulp-dev/2018-March/msg00066.html
> Pulp-dev mailing list
> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev