Issue #5645
closed
Story #5517: [EPIC] Automation Hub Release Blockers
Need to return deprecated status in collection versions endpoint
Status:
CLOSED - CURRENTRELEASE
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.
- Groomed changed from No to Yes
- Sprint set to Sprint 61
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 ?
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.
- Status changed from NEW to POST
- Assignee set to daviddavis
- Status changed from POST to MODIFIED
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
Expose collection deprecated and deprecated filter
fixes #5645 https://pulp.plan.io/issues/5645