<div dir="ltr"><span style="font-size:12.800000190734863px">> A configuration file in the user's home dir, right?</span><br><div><span style="font-size:12.800000190734863px"><br></span></div><div><span style="font-size:12.800000190734863px">Yes, exactly.</span></div><div><span style="font-size:12.800000190734863px"><br></span></div><div><span style="font-size:12.800000190734863px">> </span><span style="font-size:12.800000190734863px">"View" as in - press any key for the next page?</span></div><span class="gmail-im" style="font-size:12.800000190734863px"><br></span><div><span class="gmail-im" style="font-size:12.800000190734863px">We’re kind of leaving this up in the air for now. Optimally, we would have something like you mention where you press a key to go to the next page. However, we might just spit out all results (like pulp-admin currently does) for the MVP and add better support for pagination in 3.1+.</span></div><div><span class="gmail-im" style="font-size:12.800000190734863px"><br></span></div><div><span class="gmail-im" style="font-size:12.800000190734863px">> </span><span style="font-size:12.800000190734863px">Like "$ pulp -h" and "$ pulp repository -h”?</span></div><div><span style="font-size:12.800000190734863px"><br></span></div><div><span style="font-size:12.800000190734863px">Yes. I’m imaging this would be similar to how pulp-admin does it.</span></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="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>
<br><div class="gmail_quote">On Wed, May 2, 2018 at 3:46 PM, Jeff Ortel <span dir="ltr"><<a href="mailto:jortel@redhat.com" target="_blank">jortel@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 text="#000000" bgcolor="#FFFFFF">
Thanks for putting this together. Seems like the devil will be in
the details pending REST API decisions.<span class=""><br>
<br>
<div class="m_4863380876224920961moz-cite-prefix">On 05/02/2018 01:09 PM, David Davis
wrote:<br>
</div>
<blockquote type="cite">
<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></span>
A configuration file in the user's home dir, right?<span class=""><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>- As a user, I can view all results even if they are
paginated</div>
</div>
</div>
</blockquote>
<br></span>
"View" as in - press any key for the next page?<span class=""><br>
<br>
<blockquote type="cite">
<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></span>
Like "$ pulp -h" and "$ pulp repository -h"?<span class=""><br>
<br>
<blockquote type="cite">
<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">
<div dir="ltr">
<div>
<div><br>
</div>
<div>- As user, I have autocompletion for all commands.</div>
</div>
</div>
</blockquote>
</span><blockquote type="cite"><span class="">
<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="m_4863380876224920961gmail_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="m_4863380876224920961mimeAttachmentHeader"></fieldset>
<br>
</span><pre>______________________________<wbr>_________________
Pulp-dev mailing list
<a class="m_4863380876224920961moz-txt-link-abbreviated" href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a>
<a class="m_4863380876224920961moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/pulp-dev" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a>
</pre>
</blockquote>
<br>
</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>