Juan Luis Cano Rodríguez

Btw for my kedro-brass experiment I ended up using @alparibal 's kedro-inspect Maybe this would enable us to build a Kedro MCP server that can yield structured information about a...

Closing this as not planned.

Adding the public link instead for archival purposes https://kedro.hall.community/support-lY6wDVhxGXNY/second-runner-run-fails-to-save-output-after-pipeline-upgrade-V5X74llZ8xD1

paging @bielstela since you opened https://github.com/kedro-org/kedro-viz/issues/1714 :) before proceeding with `get_info` though (which was a strawman proposal), given that there's a [`AbstractDataset._describe`](https://github.com/kedro-org/kedro/blob/9464dc716c987ac0bcadba49aa97a4fa1ae18248/kedro/io/core.py#L373-L378), should we actually have a `describe` for this...

Would love to know @merelcht and @rashidakanchwala opinion before proceeding

(Specifically, whether we should add a dedicated public `get_info` or if it should be `describe` and wrap `_describe`)

We discussed this in backlog grooming and we acknowledge that the original problem (that Viz needs private data from datasets https://github.com/kedro-org/kedro-viz/issues/1893#issuecomment-2432719034) exists and we want to address it. There was...

Notice this was already identified as a user pain point in https://github.com/kedro-org/kedro/issues/3936

> As a Kedro user I have always wanted to be able to define modular pipelines in a config file. And you're not alone! Your data team will go through...

Notice that this is a departure from your original request - that `pipelines.yml` live under `conf/`. This is based on the opinion I stated in https://github.com/kedro-org/kedro/pull/3904#issuecomment-2149024266 - but again, your...