Create or update a Flow.
Flows can also be identified by the ID
or their path
.
If you provide a commit message, then the new version will be committed; otherwise it will be uncommitted. If you try to commit an already committed version, an exception will be raised.
A key-value object identifying the Flow Version.
Path of the Flow, including the name. This locates the Flow in the Humanloop filesystem and is used as as a unique identifier. For example: folder/name
or just name
.
ID for an existing Flow.
Message describing the changes made.
Path of the Flow, including the name, which is used as a unique identifier.
Unique identifier for the Flow. Starts with fl_.
A key-value object identifying the Flow Version.
Name of the Flow.
Unique identifier for the specific Flow Version. If no query params provided, the default deployed Flow Version is returned.
The status of the Flow Version.
The number of logs that have been generated for this Flow Version
ID of the directory that the file is in on Humanloop.
Message describing the changes made. If provided, a committed version of the Flow is created. Otherwise, an uncommitted version is created.
The list of environments the Flow Version is deployed to.
The user who created the Flow.
Aggregation of Evaluator results for the Flow Version.
The list of Monitoring Evaluators associated with the Flow Version.