What do you want from the session? The answer this question will likely be lifecycle hooks

I want the session_id

So is that not equivalent to the

run_id

here?

Yes, I guess that is the same

This change is very intentional because it makes state very difficult manage in single vs multi-process mode

I could also read that was the reason you removed it

if you find yourself having to make a node aware of the lifecycle then my guess is that you need a hook

Okay, I understand the reasoning

💪

Sometimes it is just nice to mark e.g. a plot with a run_id

Super thanks 👍

it's a little clunky as you'll need to map it override an existing dataset

arh yes - how do you do that?

so in you

before_pipeline_run

hook you do

os.environ['KEDRO_RUN_ID']

and then retrieve it with

os.environ.get('KEDRO_RUN_ID')

Okay, using the pipeline hook. Nice

👍

Sorry, I got it to work now with a sequencialrunner, but what do you mean with "then wrap the 'getter' in a plot_runid() method so you dont write it over and over"?

so wrap your plotting logic in a function

The plotting functionality is placed in a custom dataset - basically passing the plotly.go.Figure object to a custom dataset that saves it as json, html and png

ah so you can define this in the custom dataset

yes - this way I have a version on the plot. I just want to add the version as text in the plot as well. Good to know when sharing between co-workers

💪