Pulp CLI

Story #6607

As a CLI user, I can provide a configuration with my authentication credentials and server address

Author: daviddavis

Story #6608

As a CLI user, I can reference resources by name or pulp_href.

Author: daviddavis

Story #6609

As a CLI user, I can see details of a task

Author: daviddavis

Story #6610

As a CLI user, I can cancel a running or waiting task

Author: daviddavis

Story #6611

As a CLI user, I am guaranteed that the CLI will wait on tasks to complete

Author: daviddavis

Story #6612

As a CLI user, server responses shown to me are parsed to human readable form

Author: daviddavis

Story #6613

As a CLI user, I can chunk upload artifacts into Pulp

Author: daviddavis

Story #6614

As a CLI user, I have docs on how to install, setup, and use the Pulp CLI

Author: daviddavis

Story #6615

As a user, I can interact with pulp_file

Author: daviddavis

Story #6616

As a plugin writer, I can ship custom CLI commands that are discovered by a Python entry point

Author: daviddavis

Story #6617

As a plugin writer, I am guaranteed that all API endpoints for a plugin are automatically availab...

Author: daviddavis

Story #6618

As a plugin writer, I can use the plugin template (or similar tool) to get a basic code structure...

Author: daviddavis

Story #6619

As a plugin writer, I can use the plugin template (or similar tool) to generate CI/CD for testing...

Author: daviddavis

Story #6620

As a plugin writer, I have docs on how to setup and create CLI commands

Author: daviddavis

Story #6626

As a user, I can sync, publish, and distribute a file repository using one command

Author: daviddavis

Story #6668

As a plugin writer, I can write tests for my CLI

Author: daviddavis

Story #6606

As a CLI user, can see status of Pulp

Author: daviddavis

mdellweg