Introduce CONTENT_ORIGIN as a required setting
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.
Add a setting named CONTENT_ORIGIN that is required.
Set content_origin to the 1st node's 1st address.
If not set by the user.
Limited scope (single-node clusters), but sufficient for
minikube/k3s/our Travis CI.
In pulp-operator, the content_origin should be set to the actual accessible service URL
Introduce CONTENT_ORIGIN setting
This also adds a check that the user specified CONTENT_ORIGIN at
startup. Pulp refuses to start if it is not set with an error message
for the user.
Set CONTENT_ORIGIN settings
The Travis environment needs `content_origin` set as a setting.
This also updates the tests to expect Pulp's Distribution.base_url to
provide absolute urls.
- Status changed from POST to MODIFIED
Applied in changeset pulp_file:74acaf3c4f679c4e888d18092c2a505764a0e317.
Please register to edit this issue