<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<div class="moz-cite-prefix">On 2/19/19 6:38 AM, Ina Panova wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAKOB80t0wY3tWO4P+QZdux9a3ideOsKLoRUcxLgAKZFcuzmSSw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>+1 to facilitate the upload process.</div>
<div>At the conferences, there have been many users pointing out
how inconvenient current upload process is .<br>
</div>
</div>
</blockquote>
<p>Is it so much more inconvenient because pulp3 doesn't have a cli?</p>
<p>Justin</p>
<blockquote type="cite"
cite="mid:CAKOB80t0wY3tWO4P+QZdux9a3ideOsKLoRUcxLgAKZFcuzmSSw@mail.gmail.com">
<div dir="ltr">
<div>
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr"><br>
<br>
--------<br>
Regards,<br>
<br>
Ina Panova<br>
Software Engineer| Pulp| Red Hat Inc.<br>
<br>
"Do not go where the path may lead,<br>
go instead where there is no path and leave a trail."<br>
</div>
</div>
</div>
<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Feb 18, 2019 at 8:42
PM Austin Macdonald <<a href="mailto:austin@redhat.com"
moz-do-not-send="true">austin@redhat.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>Originally, our upload story was as follows:</div>
<div>The user will upload a new file to Pulp via POST to
/artifacts/ (provided by core)<br>
</div>
<div>The user will create a new plugin specific Content via
POST to /path/to/plugin/content/, referencing whatever
artifacts that are contained, and whatever fields are
expected for the new content.<br>
</div>
<div>The user will add the new content to a repository via
POST to /repositories/1/versions/<br>
</div>
<div><br>
</div>
<div>However, this is somewhat cumbersome to the user with 3
API calls to accomplish something that only took one call
in Pulp 2. <br>
</div>
<div><br>
</div>
<div>There are a couple of different paths plugins have
taken to improve the user experience:</div>
<div>The Python plugin follows the above workflow, but reads
the Artifact file to determine the values for the fields.
The RPM plugin has gone even farther and created a new
endpoint for "one shot" upload that perform all of this in
a single call. I think it is likely that the Python plugin
will move more in the "one shot" direction, and other
plugins will probably follow.<br>
</div>
<div><br>
</div>
<div>That said, I think we should discuss this as a
community to encourage plugins to behave similarly, and
because there may also be a possibility for sharing some
of code. It is my hope that a "one shot upload" could do 2
things: 1) Upload and create Content. 2) Optionally add
that content to repositories.</div>
</div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank"
moz-do-not-send="true">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Pulp-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/pulp-dev">https://www.redhat.com/mailman/listinfo/pulp-dev</a>
</pre>
</blockquote>
</body>
</html>