Hey guys, I have a question regarding the new OmegaConfLoader class. Currently, we have a custom config loader implemented (based on the templated one), but we are considering to switch if we can replicate the existing functionality somehow. Currently, we have a

conf/base/globals.yml

file where we store placeholder values to be filled up by env vars. these variables are then used in our catalog. We use those to be able to overwrite prefixes on the fly. This is useful for us when we want to test changed E2E in isolation (e.g using the Jira issue number in the prefix instead of

prod

). I was wondering if we could somehow replicate the behaviour (maybe by overwriting the globals with a

conf/local/globals.yml

?)

Hey Matthias, you can do it now with globals in OmegaConfigLoader - https://docs.kedro.org/en/stable/configuration/advanced_configuration.html#how-to-use-global-variables-with-the-omegaconfigloader

I indeed figured that out. And adding them to globals nicely does the trick