Story: Organize content by repository

[ ] Enable admins to create, update and delete repositories. #210 #215
[ ] Support two repository types: sync and modify. Sync repositories pull content in from an external AH instance (e.g., Community Hub, AH Cloud, another private AH) and are read only. Modify repositories can be used for CLI publish, install and promote operations. #210
[ ] When content is published or promoted to a modify type repository, the AH import process runs against the content. #211
[ ] Compartmentalize the import process so that there are base checks (things we always run), optional platform checks (i.e., checking for a README), and an optional run of sanity tests. #211
[ ] Configure importer options at the repository level (i.e., turn on or off optional platforms checks and sanity tests). #211
[ ] Expose repositories via URL path. For example, to publish a collection to repository-a, a user would publish to /api/v3/repository-a/artifacts/collections. #210
[ ] Add a collection promote command to the CLI that copies content from one repository to another. #212, #217
[ ] Add RBAC to repositories that controls Read and Write access for users and teams. #213 #214
[ ] Continue to support the single repository model in AH Cloud (i.e., leave AH Cloud the way it is)
[ ] When content comes into a modify type repository (either through publish or promotion), automatically create a new namespace, if it does not already exist. Namespaces will be unique within a repository. Example: When user promotes geerlingguy.foo from the Community sync repo to a modify repo, the geerlingguy namespace is automatically created. #216
[ ] When searching for and viewing content in the UI, enable the user to select a repository from their list of accessible repositories. #218

ansible / galaxy-dev

Story: Organize content by repository #208