dynaconf_include definition precedence

When using dynaconf_include inside a configuration file, the imported file seems to get precedence over the file the inclusion is done from. Is there a way to reverse this behavior?

Example:

base_config.yml:

default:
  val: 1

extension_config.yml:

default:
  dynaconf_include:
  - base_config.yml
  val: 2

If one now uses extension_config.yml, val will give 1 (the value defined in base_config.yml), while I would like it to give 2 instead (the value defined in extension_config.yml.

[aberres]

FWIW now I finally realized (as described above) that I can solve my problem by defining PRELOAD_FOR_DYNACONF instead of DYNACONF_INCLUDE. Works like a charm 🎊

[rochacbruno]

Lots of things changed on 3.0.0 and this issue is still required