Task #5629
closed
Introduce CONTENT_ORIGIN as a required setting
Status:
CLOSED - CURRENTRELEASE
Estimated time:
(Total: 0:00 h)
Description
As discussed on the mailing list we need a new required setting because:
1. plugins like pulp_docker require this CONTENT_HOST to be set, but others may not, so this setting could become a dividing line for plugins that want it set versus those that don't.
2. Clients are semantically unsure how to handle responses for one Pulp server versus another. This setting changes the client's responsibilities (relative vs absolute URL handling).
3. Relative urls are not as usable as absolute urls.
Solution¶
Add a setting named CONTENT_ORIGIN that is required.
This is a 3.0 GA blocker. Adding to sprint.
- Status changed from NEW to ASSIGNED
- Assignee set to bmbouter
- Tracker changed from Issue to Task
- % Done set to 0
- Subject changed from Rename CONTENT_HOST to CONTENT_ORIGIN to Introduce CONTENT_ORIGIN as a required setting
- Description updated (diff)
- Status changed from ASSIGNED to NEW
- Assignee deleted (
bmbouter)
- Subject changed from Introduce CONTENT_ORIGIN as a required setting to [Epic] Introduce CONTENT_ORIGIN as a required setting
- Subject changed from [Epic] Introduce CONTENT_ORIGIN as a required setting to Introduce CONTENT_ORIGIN as a required setting
- Status changed from NEW to ASSIGNED
- Assignee set to daviddavis
- Status changed from ASSIGNED to MODIFIED
- Status changed from MODIFIED to POST
- Status changed from POST to MODIFIED
- Status changed from MODIFIED to POST
- Status changed from POST to MODIFIED
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
Set content_origin automatically
The plugin_template sets
content_origin
as http://$(hostname):24816`. This aligns with the current way services are tested on Travishttps://pulp.plan.io/issues/5629 re #5629