Project

Profile

Help

Issue #5645

Story #5517: [EPIC] Automation Hub Release Blockers

Need to return deprecated status in collection versions endpoint

Added by newswangerd about 1 year ago. Updated 2 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 61
Quarter:

Description

On the /pulp/api/v3/content/ansible/collection_versions/ endpoint add the following:

  • Add the deprecation status of the collection that each version is part of.
  • Add a ?deprecated=true|false param to the to filter out versions that are part of a deprecated collection. If ?deprecated=true versions should only be returned that are part of a deprecated collection. If ?deprecated=false versions that are not part of a deprecated collection should be returned. If the param is not set, all versions should be returned.

Associated revisions

Revision 5ee426ef View on GitHub
Added by daviddavis about 1 year ago

Expose collection deprecated and deprecated filter

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

History

#1 Updated by daviddavis about 1 year ago

  • Groomed changed from No to Yes
  • Sprint set to Sprint 61

#2 Updated by bmbouter about 1 year ago

Part of the challenge is that at the model layer "depcrecation" is on Collection not CollectionVersion. We could have the viewset and serializer fulfill this, but I want to confirm you don't want this moved in the db also.

Also can't we use the filtering using _ notation to provide the filtering as /foo/bar/versions/?collection_deprecated=true|false ?

#3 Updated by newswangerd about 1 year ago

Part of the challenge is that at the model layer "depcrecation" is on Collection not CollectionVersion. We could have the viewset and serializer fulfill this, but I want to confirm you don't want this moved in the db also.

We don't need the deprecation status added to the database for collection versions.

Also can't we use the filtering using _ notation to provide the filtering as /foo/bar/versions/?collection_deprecated=true|false ?

&collection__deprecated=true returned this:

{
    "errors": [
        "Invalid Filter: 'collection__deprecated'"
    ]
}

Not sure if I'm doing something wrong or it's just not supported.

#4 Updated by daviddavis about 1 year ago

  • Status changed from NEW to POST
  • Assignee set to daviddavis

#5 Updated by daviddavis about 1 year ago

  • Status changed from POST to MODIFIED

#6 Updated by bmbouter 2 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF