Issue #3981
Updated by bmbouter about 6 years ago
h3. Problem The .yaml format for the settings file is creating several challenges: * Users will have to have a separate Python file anyway for RQ. See https://pulp.plan.io/issues/3980 * We point users to the "Django docs" but all of those examples are for Python formatted configs. The user then has to translate these back to Yaml. This creates tickets like this: https://pulp.plan.io/issues/3618#note-3 * You can interpret runtime variables in Python, resolving issues like this: https://pulp.plan.io/issues/3943#note-3 * We can still support top-level "overwriting" by having the module settings overwrite default ones. That would resolve this: https://pulp.plan.io/issues/3879 h3. Proposal: Make it just like a Django settings file that uses all-caps module-level attributes. It's just like there: https://docs.djangoproject.com/en/2.1/ref/settings/ Have Pulp use the Dynaconf Django: plugin.https://dynaconf.readthedocs.io/en/latest/guides/django.html#settings-files Update user's settings file overlay on top of the docs so the users know they can use dynaconf to configure default Pulp with. one. This would easily resolve https://pulp.plan.io/issues/3879
.