Hey guys, could you clarify if it's expected behavior that when you provide custom

CONFIG_LOADER_ARGS

in

settings.py

, some default keys get overwritten—even if you don’t explicitly override them? For example, if you set

CONFIG_LOADER_ARGS

to an empty dict, or only update something (e.g. the

config_patterns

), the

base_env

becomes empty. So something like:

CONFIG_LOADER_ARGS = {}
# or
CONFIG_LOADER_ARGS = {
    "config_patterns": {
        "globals": ["globals*", "globals*/**", "**/globals*"],
    }
}

breaks the configuration loading because

base_env

ends up being

None

. I’m asking because I expected

CONFIG_LOADER_ARGS

to act as an update to the default values, not a full replacement. From what I’ve seen with other keys, it seems like that is how it works—for example, other patterns remain intact even if you don’t include them in your custom

CONFIG_LOADER_ARGS

.

Hey, yeah, you do have to specify

base_env

and

default_run_env

arguments to

CONFIG_LOADER_ARGS

if you update them in

settings.py

. This changed in Kedro 0.19 afaik and is expected behaviour now!

Got it, thanks for the clarification!