@rochacbruno @jyejare It looks like this has broken integration with environment variables.

If I have dynaconf 3.1.8 installed, and the combination of:

1. settings.yaml field key (nested one level from top map) is present, value is empty
2. validator with default=None for given field key
3. envvar set for nested field key (DYNACONF_something__field_key)
4. settings object configuration that looks like: https://github.com/SatelliteQE/robottelo/blob/master/robottelo/config/__init__.py#L18

My envvar value is no longer set in the resulting box instance, it takes the validator default of None.

I confirmed its this line in particular by modifying the file in site-packages with 3.1.8 installed.

Originally posted by @mshriver in https://github.com/rochacbruno/dynaconf/pull/729#discussion_r853220515