Task #3696
closed
Story #3693: Lazy for Pulp3
Add the streamer's settings to settings.yaml in the content app area
Status:
CLOSED - CURRENTRELEASE
Description
These settings would be added to the settings.py and server.yaml file with defaults.
redirect_host: The hostname to use when redirecting the client. This is required when using lazy.
redirect_port: The port to use when redirecting the client. This is required when using lazy.
redirect_prefix_path: The prefix path to prepend the to the URL when redirecting. This allows you to reroot squid. Defaults to None.
https_retrieval: If true, use https as the protocol the client should use, otherwise http. Defaults to True.
- Subject changed from Add the squid settings to settings.yaml in the content app area to Add the streamer's settings to settings.yaml in the content app area
squid's config is read by squid.conf and is in another story.
What exactly are the settings we need? I think this ticket still needs that level of planning.
The following settings from pulp 2 are applicable to pulp 3.
[lazy]
- redirect_host:
- redirect_port:
- redirect_path:
- https_retrieval: true
- Description updated (diff)
I agree those are the right settings. I'm adding them to the description along with some descriptions.
I renamed redirect_path to redirect_prefix_path because I thought it more clearly called out that it's only the prefix. I believe that's correct.
I want to retell what I think https_retrieval does for the users. It allows them to force https or http to match how they've configured their squid. It's a global setting which is kind of unfortunate because if you have some clients that can't support https you have to disable https globally. At some point in the future we may consider an option that would allow this setting at a distribution level.
Also for https_retrieval, we can't rely on "use the same protocol the client used to contact Pulp with" because when deploying Pulp behind a reverse proxy that provides TLS termination (for example) would always appear to pulp as http when the client is actually requesting https.
- Description updated (diff)
- Groomed changed from No to Yes
- Sprint Candidate changed from No to Yes
Added a default for https_retrieval.
- Blocks Task #3697: Have Pulp do a simple redirect (no signing) to squid when the content app needs to serve a RemoteArtifact added
- Status changed from NEW to ASSIGNED
- Assignee set to jortel@redhat.com
The redirect settings pertain to the content app and should be added under the existing CONTENT section.
- Status changed from ASSIGNED to POST
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
- Sprint/Milestone set to 3.0.0
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
Support redirect in the content application. closes #3696, #3697