Joel

So this falls under a wider topic we have about custom `session_id`s. It was also identified in our #3094 MLOps research. We have a weird constraint that `session_id`/versioning needs to...

could you elaborate on what this would help you achieve?

I'm trying to think about how this could work - as part of @ElenaKhaustova and @iamelijahko 's excellent `DataCatalog` research (https://github.com/kedro-org/kedro/issues/3934) there is now an initiative to make a consistent...

How would you like this to work if it existed? Is it based on a condition or is it known pre-run?

Hey @lvijnck good to see you pop up here 👀 congrats on the new role! The current way to do this is to pass a dummy dataset between the nodes...

This was the issue (now discussion) I was looking for, @lvijnck if you have any further thoughts please add them there as it really helps prioritise things https://github.com/kedro-org/kedro/discussions/3758

Related - https://github.com/kedro-org/kedro/issues/2552

This is a great point, I _think_ the other slightly more robust way to do this would is to add a `logging.info(response.text)` call so that this sort of stuff can...

That makes sense, I think the ambition is right, we should store this. I guess this was built under the assumption we only cared about `200` responses, but `POST` functionality...

before you do any work - I'd maybe like to get some other contributors opinion! @noklam @merelcht any thoughts here?