Any easy way to set your default pipeline according to your configuration environment? Example: • if

--env=local

, default= p1+p2 • if

--env=prod

, default =p1

I think the easiest way is to set the env via the

KEDRO_ENV

env var and then pick that var up in the pipeline registry

I would argue this is not ideal and too much magic. Why not having separate pipeline registry and have kedro run --env=prod --pipeline=prod?

Those are good points. @Nok Lam Chan I was trying to avoid having to specify the pipeline and have that handled in the background, but indeed could be a lot of dynamic behavior on the registry. Will check both options, thanks guys!

In production environment, the ability to debug quickly is more important. If there are few arguments that you don’t want to type every single time. Either use the config option or I would just go for alias like Makefile. This way you keep everything explicit and development easy