Pulp

https://github.com/pulp/pulp/pull/3498

So, the naming convention for yaml is all lower_snake_case. However, Django settings expect UPPERCASE for some of the values like DEBUG and while we could add logic to places to account for this, for future proofing later additions to the yaml file not already existing or commented out in the yaml file, it would probably be wise to simply go with UPPERCASE in the yaml to maintain consistency with Django's settings.py expectations. This does not break anything for yaml and prevents bugs on the Django side.

Just to prevent going down this naming convention train of thought in the future and replicating research, we should also add a comment to the yaml file explaining the naming convention reasoning here.

Is having our code convert the yaml settings from lower_snake_case to UPPER_SNAKE_CASE an option?

Another question: is not using yaml an option?

Are we already?
dalley pointed this out earlier: https://github.com/pulp/pulp/blob/3.0-dev/pulpcore/pulpcore/app/settings.py#L271

Yup, I do think that's what our code is already doing.

The thing is, since our yaml file is really just a thin wrapper around Django's settings.py variables, it would be best to stick close to Django for the simple reason that it makes comparing the settings with the Django docs easier.

The thing is, since our yaml file is really just a thin wrapper around Django's settings.py variables

I disagree. We have a number of other settings besides the ones we pass to Django like for our redis config, media root, content app, etc.

That said, it doesn't look like there's a prescriptive format for yaml though.

MEDIA_ROOT is a django setting though?

https://docs.djangoproject.com/en/2.0/ref/settings/#media-root

Sorry, I meant working directory:

https://github.com/pulp/pulp/blob/3.0-dev/pulpcore/pulpcore/etc/pulp/server.yaml#L93