DagsterDeployedFlow class represents a Metaflow flow that has been deployed as a Dagster definitions file. It provides methods to trigger new runs and manage the deployment.
Properties
Deployment identifier encoding all info needed for
from_deployment.Returns deployer.name directly: the create command embeds the full JSON blob (name, flow_name, flow_file, definitions_file) so the identifier is self-contained and survives a process restart.Human-readable job name extracted from the deployment identifier.This is parsed from the JSON identifier blob during initialization for display purposes.
Methods
run
Trigger a new run of this deployed flow.Flow parameters as keyword arguments (e.g.
message="hello").DagsterTriggeredRun - A triggered run object that can be used to monitor the run status.
Example
trigger
Alias forrun(). Kept for backwards compatibility.
Flow parameters as keyword arguments.
DagsterTriggeredRun
from_deployment
Recover aDagsterDeployedFlow from a deployment identifier.
The JSON string returned by
deployed_flow.deployer.name or deployed_flow.id, which contains the full deployment info (flow_file, name, flow_name, definitions_file).Optional metadata to associate with the recovered deployment.
DagsterDeployedFlow - A deployed flow instance reconstructed from the identifier.
Raises: ValueError if the identifier is invalid or missing required fields.
Example
Relationship with Deployer
TheDagsterDeployedFlow is returned by the Dagster deployer’s create() method:
deployed_flow.id contains all necessary information to reconstruct the deployment later using from_deployment(), making it easy to persist and restore deployments across process restarts.