Hello @loomlike seems this doc should get updated as well https://feathr-ai.github.io/feathr/how-to-guides/feathr-configuration-and-env.html#configuration-and-environment-variables-in-feathr

Can I ask is there any use case for introducing this new env? Have this new flag can make configuration more flexible but it introduces complexity on configuration code as well.

Hello @loomlike seems this doc should get updated as well https://feathr-ai.github.io/feathr/how-to-guides/feathr-configuration-and-env.html#configuration-and-environment-variables-in-feathr

Can I ask is there any use case for introducing this new env? Have this new flag can make configuration more flexible but it introduces complexity on configuration code as well.

The default behavior is to override the config file values (use_env_vars=True) with env variables, so I think we can keep the document as it is.
Usecases are mostly for us to test with different configuration of the client, since if we change the env var of the test machine for each test case, it's not safe (someone can forget to put the original env var back at the end of the test) as well as parallel testing will not work as they'll share the env vars.