Project

Profile

Help

Refactor #3151

closed

Pulp3 server.yaml configuration names should be standardized

Added by bizhang over 6 years ago. Updated about 5 years ago.

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

0%

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

Description

Currently we have a mix of casenames in the server.yaml.

the JWT settings are capitalized, and the rest of things are all lowercased. [0]
Django requires all settings to be uppercase [1], we do that right now by converting the settings to uppercase on load time [2]

Personally I've not seen any yaml file with UPPERCASE settings so that might be unconventional, and what we're doing might be the right thing. In any case we should standardize our config names, whether through lowercasing the JWT configs, or capitalizing the rest of the settings

[0] https://github.com/pulp/pulp/blob/961529a3ef67dbce8d49bc45e09dfd5da2171f86/pulpcore/pulpcore/etc/pulp/server.yaml
[1] https://docs.djangoproject.com/en/1.11/topics/settings/#creating-your-own-settings
[2] https://github.com/pulp/pulp/blob/961529a3ef67dbce8d49bc45e09dfd5da2171f86/pulpcore/pulpcore/app/settings.py#L285


Related issues

Related to Pulp - Issue #3589: Settings in server.yaml have inconsistent namesCLOSED - CURRENTRELEASECodeHeelerActions

Also available in: Atom PDF