Project

Profile

Help

Story #5520

closed

Story #5517: [EPIC] Automation Hub Release Blockers

As a user using a non-Galaxy API, I have a collection viewset

Added by bmbouter about 3 years ago. Updated about 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 60
Quarter:

Description

Problem

As a user with Collection content in pulp_ansible I should be able to list the Collection by namespace and name without querying for the CollectionVersion viewset.

Solution

Add a Viewset that will expose the Collection Model at /pulp/api/v3/ansible/collections/

It would allow read-only views to start with, and filterable by either namespace, name, or both.

Actions #1

Updated by bmbouter about 3 years ago

  • Parent task set to #5517
Actions #2

Updated by daviddavis about 3 years ago

  • Groomed changed from No to Yes
  • Sprint set to Sprint 60
Actions #3

Updated by daviddavis about 3 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to daviddavis
Actions #4

Updated by daviddavis about 3 years ago

  • Status changed from ASSIGNED to POST

Added by daviddavis about 3 years ago

Revision 5319d51c

Add ansible collection viewset

fixes #5520 https://pulp.plan.io/issues/5520

Actions #5

Updated by daviddavis about 3 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #6

Updated by bmbouter about 2 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF