[Pulp-list] Pulp CLI feedback

[Alejandro Cortina]

> - What commands or functionality in the CLI do you rely on the most?
pulp-admin rpm repo sync status/run --repo-id=REPO

> - Are there things you wish the CLI had or did?
* A more *intelligent* cli? I am syncing a repo and I wanted to check
status so I type:

*  pulp-admin rpm repo sync status REPO *<- error
  oh right,
  *pulp-admin rpm repo sync status --repo-id=REPO*

  Would it be possible for the cli to catch the repo-id, task-id,
something-something-id without need to specify?

* a modifier to print status in the end of the sync run
I kick-off jobs with jenkins, and every time the progress bar moves or RPM
count is updated it creates a new line, making the jenkins console
unreadable

> - Why do you use the CLI over using the REST API directly?
I learnt to use the CLI and when I discovered the REST API I was already
used to the CLI.

> - Do you strictly use the CLI or do you use other things like Katello or
the REST API?
I normally use with Katello
I use CLI for specific tasks
I tried to use Ansible but pulp_repo module fails for bit syncs and the CLI
is solid
I use the REST API with jenkins to query sync results and send report to
our chat-room

> - Would you prefer a CLI or a basic web UI?
I love the cli and the commands I already have muscle memorized. A basic
web UI would be awesome but not as replacement.

Cheers,

On Wed, May 23, 2018 at 10:39 PM, Matthew Montgomery (mattmont) <
mattmont at cisco.com> wrote:

>
> > On May 23, 2018, at 7:51 AM, David Davis <daviddavis at redhat.com> wrote:
> >
> > As many of you know by now, we're working on Pulp 3.0. With this new
> rewrite of Pulp comes the opportunity to revisit our CLI. In doing so, we'd
> like some feedback from our users on how they use the CLI and how we can
> improve on the Pulp 2 CLI.
> >
> > Here are some questions we've come up with. General feedback is welcome
> as well.
> >
> > - What commands or functionality in the CLI do you rely on the most?
>
> We mostly use the REST API with a custom Python CLI we have written to
> implement our workflows. That said, I'll still use pulp-admin from our
> master Pulp server for certain things e.g. examining a repo, manual orphan
> cleanup, repo and content deletes.
>
> > - Are there things you wish the CLI had or did?
>
> The grouping feature that was previously mentioned would be nice to have
> natively for syncing. We have Ansible playbooks that implement grouped
> syncing but it is still just iterating over a config file and syncing each
> individual member repo one after another.
>
> I'd also love to have the ability to set a repo to read only. There are
> times when we want to completely freeze updates to a release repo and have
> had developers accidentally publish new builds there.
>
> > - Why do you use the CLI over using the REST API directly?
>
> I'll use the CLI at times when I have a simple task I need to do. The tool
> we wrote that interacts with the REST API mainly composes different command
> steps for a specific goal. For example, we make a lot of repo snapshots
> which entails syncing the source repo, creating a new target repo named
> using a UTC timestamp and then copying the source repo into the new target
> repo. So our tool exposes things like this as a single command.
>
> > - Do you strictly use the CLI or do you use other things like Katello or
> the REST API?
>
> Just the CLI and the REST API.
>
> > - Would you prefer a CLI or a basic web UI?
>
> CLI is much more preferable than a basic web UI for us but I can certainly
> envision where a basic web UI might come in handy.
>
> --
> Matthew
>
>
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20180524/6c379b70/attachment.htm>