<div dir="ltr"><div>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.<br><br></div>--Dana<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>
<p style="font-weight:bold;margin:0;padding:0;font-size:14px;text-transform:uppercase;margin-bottom:0"><span>Dana</span> <span>Walker</span></p>
<p style="font-weight:normal;font-size:10px;margin:0px 0px 4px;text-transform:uppercase"><span>Associate Software Engineer</span><span style="font-weight:normal;color:#aaa;margin:0"></span></p>
<p style="font-weight:normal;margin:0;font-size:10px;color:#999"><a style="color:#0088ce;font-size:10px;margin:0;text-decoration:none;font-family:'overpass',sans-serif" href="https://www.redhat.com" target="_blank">Red Hat <span><br><br></span></a></p>
<table border="0"><tbody><tr><td width="100px"><a href="https://red.ht/sig" target="_blank"> <img src="https://www.redhat.com/files/brand/email/sig-redhat.png" width="90" height="auto"></a> </td>
</tr></tbody></table>
</div></div></div></div>
<br><div class="gmail_quote">On Mon, Apr 9, 2018 at 3:18 PM, Austin Macdonald <span dir="ltr"><<a href="mailto:austin@redhat.com" target="_blank">austin@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Folks,</div><div><br></div><div>Austin, Dennis, and Milan have identified the following issues with current Pulp3 REST API design:</div><div><ul><li>Action endpoints are problematic.<br></li><ul><li>Example POST@/importers/<plugin>/sync/</li><li>They are non-RESTful and would make client code tightly coupled with the server code.</li><li>These endpoints are inconsistent with the other parts of the REST API.</li><li>DRF is not being used as intended for action endpoints so we have to implement extra code. (against the grain)</li></ul><li>We don't have a convention for where plug-in-specific, custom repository version creation endpoints.<br></li><ul><li>example POST@/api/v3/<where?>/docker/a<wbr>dd/</li><li>needs to be discoverable through the schema</li></ul><li>For direct repository version creation, plugins are not involved.<br></li><ul><li>validation correctness problem: <a href="https://pulp.plan.io/issues/3541" target="_blank">https://pulp.plan.io/issues/35<wbr>41</a></li><li>example: POST@/api/v3/repositories/<rep<wbr>ository_id>/versions/</li></ul></ul></div><div>We would like to get feedback on these issues being sound and worth resolving before we resume particular solution discussion[1].</div><div><br></div><div>Thanks,</div><div>Austin, Dennis, and Milan</div><div><br></div><div>[1] <a href="https://www.redhat.com/archives/pulp-dev/2018-March/msg00066.html" target="_blank">https://www.redhat.com/archive<wbr>s/pulp-dev/2018-March/msg00066<wbr>.html</a><br></div><div><br></div></div>
<br>______________________________<wbr>_________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a><br>
<br></blockquote></div><br></div>