Hello once again, I've tried to take advantage of the modular_pipeline configuration files but probably used it wrongly. In order to apply this to the problem I've described, I registered my "generic pipeline" twice with different names (

app1

,

app2

) and tried to set two parameter files with following the template

conf/<env>/parameters/<pipeline_name>.yml

. But it seems that upon running the pipeline

kedro run --pipeline app1

, kedro reads everything in

conf/<env>/parameters/

folder, and not only

parameters/app1.yml

.. this results in a conflict as the

parameters/app2.yml

has the same entries. Same error is raised for catalogs. So I guess it is not designed to use like this ... Could this be requested as a feature or it is fundamentally wrong.