Project

Profile

Help

Story #2538

closed

Search paths other than EL defaults for configuration

Added by sysadmind over 7 years ago. Updated about 5 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

I've been testing running pulp on systems other than EL and this was one of the major blockers to getting pulp-admin to run. Pulp assumes that certain directories and paths will exist and where certain files will be on the filesystem.

Notable Examples:
https://github.com/pulp/pulp/blob/master/client_admin/pulp/client/admin/config.py#L8 - client-admin DEFAULT config hard codes many paths like extension directory, ca_path
https://github.com/pulp/pulp/blob/master/client_admin/pulp/client/admin/config.py#L81 - this if statement assumes that several paths exist.
https://github.com/pulp/pulp/blob/master/server/pulp/server/config.py#L47 - similar to the client-admin DEFAULT config

I believe that these paths should instead default to a list of potential paths that these requirements could be found by default. This is similar in concept to how $PATH works in a shell. I think that a list of paths could be used and iterated over to find a good default value for the system before being loaded into the DEFAULT config object.


Related issues

Related to RPM Support - Task #2699: Ensure all default CA_PATH settings to work with multiple distribution default locations in Pulp3CLOSED - WONTFIX

Actions

Also available in: Atom PDF