Nok Lam Chan

@merelcht Haven't look into this in details, would the alternative be changing that WARNING message to `INFO` instead?

Make sure to read #2531 for the discussion.

I see your [comment](https://github.com/kedro-org/kedro/issues/3768#issuecomment-2034286475) here, are you going to open a PR for this?

>-1 on keeping the current logging.yml logic - whoever wants fine grained control of logs, file logging, rotation etc should be using journald, supervisor, Datadog, or whatever other solution. this...

Quick thought, this will break %load_node immediately. Having a syntax that is identical in "pipelines.py" and DataCatalog is convenient for this case. Also, what's the size of the parameters here?...

I tested with a YAML file ~2MB (100k lines), the nested logic takes less than a second.

It was marked as a bug, which I don't agree with. CLI overwrite any existing configuration is expected and consistent with other CLI i.e. `kedro run --params --config xxx.yml`. I...

@astrojuanlu I fixed the PR and is ready to be reviewed.

> ...However, is there a chance we open an issue about the underlying problem? Maybe there's something we can do at the API level to make this easier to get...

Thank you reporting this issue, we are aware of this problem and it is on at high priority to be fixed.