Inject Execution context metadata into a Python script

[anna-geller]

We can make the execution context metadata available through a context object.

Example:

import pandas as pd
from kestra import context

mylabels = context.labels
myinputs = context.inputs
myvars = context.vars
start_date = context.trigger.startDate
csv_path = context.outputs.prev_task.uri # outputs from previous tasks

df = pd.read_csv("csv_path")

[anna-geller]

We can add it as a file .kestra-execution-context.json

It cannot be just a regular env variable because it would break as soon as you have a \n or special chars in the context with env vars

Alternative option is base64-encoded env var KESTRA_CONTEXT, we can automatically decode it when loading it using kestra.context object from the pip package, but Ludo says this could exceed the regular limits of an env var (typically should be max 128 KB)

[DarshanCode2005]

Hi @anna-geller , I’d like to request this issue be assigned to me: @DarshanCode2005.
Summary of changes
I implemented a Python Execution Context API for Kestra. Key points:

• New API: context() that returns an ExecutionContext instance.
• New classes: ExecutionContext, TriggerContext, OutputsContext, OutputWrapper.
• Attribute-style access for labels, inputs, vars, trigger metadata, and previous task outputs.
• Dynamic outputs: ctx.outputs.<task_name>. (lazy/dynamic lookup).
• Dual loading of context data: preferred file .kestra-execution-context.json, fallback to base64 KESTRA_CONTEXT environment variable.
• Clear error handling for missing or invalid context.
• Unit tests included (13 tests covering expected behavior).

Files changed / created

• python/src/kestra/init.py
• python/src/kestra/exceptions.py
• python/tests/test_context.py (13 tests)
• python/example_context.py
• python/README.md
• python/setup.py

I can open the PR and request formal review as soon as this issue is assigned to me.

[anna-geller]

as said in a comment, it would need to be a file. I'll close for now as the issue is too complex, it probably needs a proposal from a core backend developer

sorry!