[Pulp-dev] Pulp CLI MVP User Stories

[David Davis]

> A configuration file in the user's home dir, right?

Yes, exactly.

> "View" as in - press any key for the next page?

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+.

> Like "$ pulp -h"  and "$ pulp repository -h”?

Yes. I’m imaging this would be similar to how pulp-admin does it.


David

On Wed, May 2, 2018 at 3:46 PM, Jeff Ortel <jortel at redhat.com> wrote:

> Thanks for putting this together.  Seems like the devil will be in the
> details pending REST API decisions.
>
> On 05/02/2018 01:09 PM, David Davis wrote:
>
> 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.
>
> - As a user, I have a set of CLI commands that match the REST API for my
> Pulp server
>   - I have parameters for each command that correspond to API resource
> parameters
>   - I also have a CLI filter for every API resource filter
>   - I have CLI commands for core and installed plugins
>   - CLI commands for plugins that aren’t installed don’t show up
> - As a user, I can configure a file with the Pulp API URI, username,
> password
>
>
> A configuration file in the user's home dir, right?
>
> - As a user, I can view all results even if they are paginated
>
>
> "View" as in - press any key for the next page?
>
> - As a user, I can view a help screen with help text from the API schema
>
>
> Like "$ pulp -h"  and "$ pulp repository -h"?
>
>
> 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:
>
>
> - As user, I have autocompletion for all commands.
>
>
> We’ve also identified stories that we’re were thinking of not handling
> with the MVP:
>
> - As a user I can see progress for async tasks and when they complete.
> - As a user, I have CLI enabled "workflows" (ie commands that hit multiple
> API endpoints) for pulpcore and plugins
>
> 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.
>
> David
>
>
> _______________________________________________
> Pulp-dev mailing listPulp-dev at redhat.comhttps://www.redhat.com/mailman/listinfo/pulp-dev
>
>
>
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20180503/4d8cfa0e/attachment.htm>