Actions
Issue #4437
closedCannot adapt BaseUrl when serving Content at a custom URL using a custom aiohttp handler
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 49
Quarter:
Description
Problem¶
Assume that A plugin writer is adding custom routes to serve their content. They likely require this because they need more control when serving an Artifact, e.g. response headers. When their Distribution serializes the base_path it will serve all Pulp content at /pulp/content/. This is correct for most Content, but not for this type which serves it at a custom route in the content app, e.g. /mycustomurl/.
The Distributor Serializer/Viewset is also not part of the plugin API which prevents the reuse of that serializer/viewset.
This was originally identified by gmbnomis in this comment
Solution¶
Make the Serializer and Viewset part of the plugin API
Actions
Problem: DistributionSerializer is too prescriptive
Solution: Add a generic BaseDistributionSerializer
re: #4435 https://pulp.plan.io/issues/4435 re: #4437 https://pulp.plan.io/issues/4437