Story #4044: As a user, I can specify a base_path and a relative_path for a Distribution - Pulp

Send by e-mail

Story #4044

As a user, I can specify a base_path and a relative_path for a Distribution

Added by dkliban@redhat.com over 1 year ago. Updated about 1 year ago.

Status:

CLOSED - NOTABUG

Priority:

Normal

Assignee:

Category:

Sprint/Milestone:

3.0.0

Start date:

Due date:

% Done:

Platform Release:

Blocks Release:

Groomed:

Yes

Sprint Candidate:

Yes

Tags:

QA Contact:

Complexity:

Smash Test:

Sprint:

Description

Problem: Distributions have to be served at /pulp/content/<base_path>/

Content types that need to be hosted outside the /pulp/content/ URL space cannot use the Distribution to make a publication available at some URL.

Solution: Add an additional 'relative_path' field to the Distribution. The 'base_path' will default to '/pulp/content/', but the user would be allowed to set it to whatever value is needed by the plugin that is serving the Distribution. The 'relative_path' would serve the role of the 'base_path' now.

The content app would need to be updated to only look through distributions that have the 'base_path' set to '/pulp/content/'.

History

#1 Updated by dkliban@redhat.com over 1 year ago

Description updated (diff)

#2 Updated by jortel@redhat.com over 1 year ago

Groomed changed from No to Yes

#3 Updated by bmbouter over 1 year ago

This looks good to me, but that will only work if those URLs are being forwarded by the webserver to Pulp's WSGI app serving those viewsets. I think that motivates Pulp being deployed at / and not nested deeper in the urlspace. Does that sound right?

FYI, we talk some about this here: https://docs.pulpproject.org/en/3.0/nightly/overview/components/webserver.html#wsgi-application