Hi guys, I want to reuse a kedro pipline with different config, deployed from the same repo. What would be a good pattern to do this? Have a separate config directory?

Use Kedro envs

This is exactly what Environment for: https://docs.kedro.org/en/stable/configuration/configuration_basics.html#configuration-environments You only need to add the config to override (provided that your other config is in

base

). You may need to set the merging strategy depending if you need a soft-merge.

Ok, what if we have multiple pipelines per deployment...so like

pipeline_a

and

pipeline_b

in `dev`/`test`/`prod`. Can we nest them or something?

You have base and other by default inherit config from it.

Kedro has a dual environment default, that is

base

+

local

(you will see that created in starters).

base

is where you would put most of your configuration in, and then if you need to override a certain parameters, you can override it in

local

.

local

is what we called a default run environment, you can change this easily just by creating a folder in the same level. When you want to use, let say,

production

instead of

local

, you can run your pipeline as

kedro run --env production

There are two different strategy how config being override (search

merge_strategy

),you can find more details in the docs.

Ok, understood, will go to namespaces for this. Thanks!