RPM Support

Motivation¶

The current structure of Workflows page is the following:

|-- Create, Sync and Publish a Repository
|-- Upload and Manage Content
       |-- Upload foo.rpm
       |-- Create rpm content from an Artifact
       |-- Add content to repository foo
       |-- Advisory upload
       |-- One shot upload
|-- Get content from Pulp
|-- Copy RPM content between repositories

There is no section to put content specific info which would be useful for users to know, like modulemd always is moved around with its artifacts, or advisory conflict resolution.
Upload part is a bit messy and needs some love.

Suggestion¶

|-- Create, Sync and Publish a Repository
|-- Upload Content
    |-- Bulk upload (describe a long way (create artifact(s), add to a repo, mention that addition can be in bulk) of uploading 
          |-- Upload artifacts
          |-- Create content from Artifacts
          |-- Add content to repository foo
     |-- One-shot upload (info about old endpoint should be removed, here should be described the content endpoint and list of content types which support is)

|-- Get content from Pulp (add details about browseable distributions)
|-- Copy RPM content between repositories (describes how to copy all content)
|-- Manage Content (create a stub page for every content, the idea is to add general info about content and then details about their specific workflows if there are any)
     |-- Package
     |-- Advisory
     |-- Modularity
     |-- Distribution Tree
     |-- Comps.xml types
     |-- Custom repository metadata

Information for each content type will be added in separate issues.