Pulp CLI

Story #6608

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

Author: daviddavis

Story #6612

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

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 #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

Issue #7531

As a CLI user, I can view a report and repair corrupted content

Author: daviddavis

Story #7652

As a CLI user, I can specify which trusted CAs to use when connecting to Pulp

Author: daviddavis

Issue #7683

As a user, I can download and verify repo content with the CLI

Author: daviddavis

Refactor #7727

Refactor tests to use settings instead of $PULP_CLI

Author: daviddavis

Issue #7743

As a developer, I have an easy way to run linting, tests, etc locally

Author: daviddavis