@Ankita Katiyar Thx. That’s how I did it so far. But not really convenient. My problem comes from the fact that we have a single pipeline / repo for all our clients. To better enforce “tenant isolation” I have organized

conf

and

data

as follow:

conf
└── client_A
    ├── base
    └── local
└── client_B
    ├── base
    └── local

data
├── client_A
│   └── 01_raw
│   └── 02_intermediate
│   └── ...
└── client_B
│   └── 01_raw
│   └── 02_intermediate
│   └── ...conf

I did so because I liked the idea of not being able to run the pipeline without being explicit about which client it should be done for… (the structure above makes it so that

kedro run

without

--conf-source

will raise an error) Another reason I did so (if I recall correctly) was to avoid having “duplicate keys” conflicts in the different yaml files across clients…

(which we haven’t added)

@Ankita Katiyar Can you help to draft an issue?

Done https://github.com/kedro-org/kedro-viz/issues/1479 🙂