<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Thanks for putting this together. Seems like the devil will be in
the details pending REST API decisions.<br>
<br>
<div class="moz-cite-prefix">On 05/02/2018 01:09 PM, David Davis
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAHa=2Wm7NDJOaoZ_FW0LiJKVz_ALmga1S1CYFT7N0MwNPyi=fg@mail.gmail.com">
<div dir="ltr">The CLI team has identified a set of user stories
that we think we should try to accomplish for the MVP. These
would be the minimum set of requirements for the MVP CLI.
<div><br>
</div>
<div>
<div>- As a user, I have a set of CLI commands that match the
REST API for my Pulp server</div>
<div> - I have parameters for each command that correspond to
API resource parameters</div>
<div> - I also have a CLI filter for every API resource
filter</div>
<div> - I have CLI commands for core and installed plugins</div>
<div> - CLI commands for plugins that aren’t installed don’t
show up</div>
<div>- As a user, I can configure a file with the Pulp API
URI, username, password</div>
</div>
</div>
</blockquote>
<br>
A configuration file in the user's home dir, right?<br>
<br>
<blockquote type="cite"
cite="mid:CAHa=2Wm7NDJOaoZ_FW0LiJKVz_ALmga1S1CYFT7N0MwNPyi=fg@mail.gmail.com">
<div dir="ltr">
<div>
<div>- As a user, I can view all results even if they are
paginated</div>
</div>
</div>
</blockquote>
<br>
"View" as in - press any key for the next page?<br>
<br>
<blockquote type="cite"
cite="mid:CAHa=2Wm7NDJOaoZ_FW0LiJKVz_ALmga1S1CYFT7N0MwNPyi=fg@mail.gmail.com">
<div dir="ltr">
<div>
<div>- As a user, I can view a help screen with help text from
the API schema</div>
</div>
</div>
</blockquote>
<br>
Like "$ pulp -h" and "$ pulp repository -h"?<br>
<br>
<blockquote type="cite"
cite="mid:CAHa=2Wm7NDJOaoZ_FW0LiJKVz_ALmga1S1CYFT7N0MwNPyi=fg@mail.gmail.com">
<div dir="ltr">
<div>
<div><br>
</div>
<div>Also, we’re investigating an autocomplete story. We might
get it for free with some of the tools we’re using, and it
might be worth supporting from the start rather then trying
to retrofit something later:</div>
</div>
</div>
</blockquote>
<blockquote type="cite"
cite="mid:CAHa=2Wm7NDJOaoZ_FW0LiJKVz_ALmga1S1CYFT7N0MwNPyi=fg@mail.gmail.com">
<div dir="ltr">
<div>
<div><br>
</div>
<div>- As user, I have autocompletion for all commands.</div>
</div>
</div>
</blockquote>
<blockquote type="cite"
cite="mid:CAHa=2Wm7NDJOaoZ_FW0LiJKVz_ALmga1S1CYFT7N0MwNPyi=fg@mail.gmail.com">
<div dir="ltr">
<div>
<div><br>
</div>
<div>We’ve also identified stories that we’re were thinking of
not handling with the MVP:</div>
<div><br>
</div>
<div>
<div>- As a user I can see progress for async tasks and when
they complete.</div>
<div>- As a user, I have CLI enabled "workflows" (ie
commands that hit multiple API endpoints) for pulpcore and
plugins</div>
</div>
<div><br>
</div>
<div>Lastly, the issue around how to identify objects from the
cli (href/UUID/name/etc) is still an ongoing discussion that
involves the bindings as well. We plan to add a user story
later for that.</div>
<div>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div><br>
</div>
<div>David<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<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>
<br>
</body>
</html>