Beste practice with config in settings.py and settings.yaml?

[mjmare]

I appreciate Dynaconf's way of having configuration values in a settings.yaml file. However, this means that some, but not all, config values "move" from settings.py to settings.yaml.
I'm struggling a bit on how to keep track of where config values are defined. Currently I comment them out in settings.py. It is a bit confusing to a new user (or future me) on where to find a specific config value.

What strategy do you use to make config values easy to locate?

[rochacbruno]

I assume you are talking about a Django project,
In that case I like to have all the mandatory keys in the settings.py before the loading of dynaconf, variables such as DEBUG, TEMPLATES, MIDDLEWARES etc...

Then after dynaconf is loaded and configured with its data sources (yaml, toml, envvars, redis etc...) all the variables belonging to my application I tend to put in the settings.yaml (given your example).

The default variables (DEBUG, MIDDLEWARES, etc) can then be overridden using the yaml or environment variables.

The next release of Dynaconf is coming with a tool #939 to allow you to track the provenance of a variable.

[mjmare]

(Django indeed!)
My issue was: do you then delete the overridden variable from settings.py? How do you indicate in settings.py that the variable is overridden in settings.yaml. Or do you?
It is one thing that in the settings.yaml file different environments might override the values from other environments. But that is within 1 file and they have the same format (YAML). But settings.py and settings.yaml are quite different.

[mjmare]

or perhaps one could move all configs from Django settings.py to the settings.yaml file. Much clearer but a lot of work.

[rochacbruno]

You can move all to the yaml.

Also you can define Validators on the settings.py

Validator("DEBUG", required=True)

[mjmare]

Thanks.
Still interested on how people approach this problem.