This message was deleted.

Right now it seems that I have to choose one or the other, and then if I want to switch I have to restart Jupyter.

yes, as you mention, the only way to switch the jupyter integration is to restart the instance which isn't great. I've been thinking that we need to introduce some sort of "ploomber config file" at the project level (since a single project may have more than one pipeline), inside that file one could specify multiple pipeline.yaml for the jupyter integration to work. thoughts?

The consolidated config is a good idea. That would help with another issue I’m seeing, which is that I’m having to duplicate certain config across multiple env.[name].yaml files. I have dev and prod env files, but certain config is common to those, such as the list of time series for which I’m training models.

what you mention about env.yaml already came up. is this what you're looking for? https://github.com/ploomber/ploomber/issues/679

Yes, exactly.