Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Makes CONTENT_ORIGIN not a required setting #6156

Closed
wants to merge 1 commit into from

Conversation

dkliban
Copy link
Member

@dkliban dkliban commented Dec 16, 2024

Related to #5931

@dkliban dkliban force-pushed the content-origin-none branch from 41f46c3 to 6e35d29 Compare January 3, 2025 19:11
@dkliban dkliban marked this pull request as ready for review January 3, 2025 19:11
Comment on lines -200 to +203
A required string containing the protocol, fqdn, and port where the content app is reachable by
A string containing the protocol, fqdn, and port where the content app is reachable by
users. This is used by `pulpcore` and various plugins when referring users to the content app.
For example if the API should refer users to content at using http to pulp.example.com on port
24816, (the content default port), you would set: `https://pulp.example.com:24816`.
24816, (the content default port), you would set: `http://pulp.example.com:24816`. The default is
`None`. When set to `None`, the API returns relative URLs (without the protocol, fqdn, and port).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now this is off wrt formatting. It's neither break at 100 c nor one sentence per line.

@bmbouter
Copy link
Member

bmbouter commented Jan 6, 2025

This work transitioned from @dkliban to @git-hyagi who needs to handle the requested changes. Unfortunately we need to close this PR and reopen a new one from hyagi's branch due to him not being a pulp/core maintainer currently. I've put a note on the pulpcore meeting agenda requesting we add him, but for today closing this PR is our only option to move forward.

@bmbouter bmbouter closed this Jan 6, 2025
@git-hyagi
Copy link
Contributor

new PR: #6175

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants