Struct BridgeContext 

pub struct BridgeContext<'a> {
    pub execution_id: i64,
    pub step: &'a str,
    pub variables: &'a HashMap<String, String>,
    pub server_url: String,
    pub worker_id: Option<String>,
    pub command_id: Option<String>,
}

Per-call context for the bridge. Groups together what would otherwise be many parameters threaded through every dispatch site.

The CLI’s ExecutionContext (repos/cli/src/playbook_runner.rs) has a different shape than ToolsExecutionContext — the CLI uses HashMap<String, String> for variables and tracks step results separately; noetl-tools uses HashMap<String, serde_json::Value> and bundles many more execution-level fields (server_url, worker_id, command_id, etc.).

BridgeContext is the narrow view the CLI hands to the bridge; to_tools_context expands it into the full ToolsExecutionContext shape.

Fields

execution_id: i64

Execution id — required by ToolsExecutionContext. CLI local mode synthesises this from the start time / playbook path; the worker uses the snowflake id from noetl.command.

step: &'a str

Step name the bridged tool is running under.

variables: &'a HashMap<String, String>

CLI variables map (workload., vars., .result, etc.).

server_url: String

Control-plane server URL. Empty string when running in CLI local mode without a server backend.

worker_id: Option<String>

Worker id / command id — None in CLI local mode.

command_id: Option<String>