@Anjali Datta I've created a quick-and-dirty example of how you can have a dynamic catalog + pipelines using Jinja (see https://docs.kedro.org/en/stable/kedro_project_setup/configuration.html#jinja2-support). This is the diff on top of just creating a new project named "Jinja Example": https://github.com/deepyaman/programmatic-pipelines/commit/cfe7b1afe5fb8e013d7b4568eaa601246538c7b5#diff-0eea4f4e49677291b[…]2cf4f017733483d62adbff5 Cons of this approach: • I've defined

regions

in two places, because you can't use something like

globals.yml

inside Jinja. • In Kedro 0.19, I think a new OmegaConfLoader will be the preferred way to go, and I don't think that support Jinja. I'm not 100% sure how this use case would be best handled there. • Too much Jinja makes pipelines confusing (I think this use case for reused modular pipelines is fair, though). If you aren't familiar with namespacing/reuse of modular pipelines, see https://docs.kedro.org/en/stable/nodes_and_pipelines/modular_pipelines.html#using-the-modular-pipeline-wrapper-to-provide-overrides I can try and add an example of keeping the pipeline definition in Python and using with pipelines as an alternative, even though i don't think it's well documented P.S. I used Kedro 0.18.6, which includes some stuff like pipeline autodiscovery (https://docs.kedro.org/en/stable/nodes_and_pipelines/pipeline_registry.html#pipeline-autodiscovery); if you try to replicate with 0.17.7, you will need to add "data_processing" explicitly