MVP 0% 14 issues (0 closed — 14 open) Related issues Story #6606: As a CLI user, can see status of Pulp Actions Story #6607: As a CLI user, I can provide a configuration with my authentication credentials and server address Actions Story #6608: As a CLI user, I can reference resources by name or pulp_href. Actions Story #6609: As a CLI user, I can see details of a task Actions Story #6610: As a CLI user, I can cancel a running or waiting task Actions Story #6611: As a CLI user, I am guaranteed that the CLI will wait on tasks to complete Actions Story #6612: As a CLI user, server responses shown to me are parsed to human readable form Actions Story #6614: As a CLI user, I have docs on how to install, setup, and use the Pulp CLI Actions Story #6615: As a user, I can interact with pulp_file Actions Story #6616: As a plugin writer, I can ship custom CLI commands that are discovered by a Python entry point Actions Story #6617: As a plugin writer, I am guaranteed that all API endpoints for a plugin are automatically available by the CLI parsing the openAPI schema Actions Story #6618: As a plugin writer, I can use the plugin template (or similar tool) to get a basic code structure for my CLI package Actions Story #6619: As a plugin writer, I can use the plugin template (or similar tool) to generate CI/CD for testing and releasing my CLI package Actions Story #6620: As a plugin writer, I have docs on how to setup and create CLI commands Actions
.
.
.