Headers
Path Parameters
The name of the flow
The name of the deployment
Response
Successful Response
The name of the deployment.
The flow id associated with the deployment.
An optional version for the deployment.
A description for the deployment.
A schedule for the deployment.
A schedule formed by adding interval
increments to an anchor_date
. If no
anchor_date
is supplied, the current UTC time is used. If a
timezone-naive datetime is provided for anchor_date
, it is assumed to be
in the schedule's timezone (or UTC). Even if supplied with an IANA timezone,
anchor dates are always stored as UTC offsets, so a timezone
can be
provided to determine localization behaviors like DST boundary handling. If
none is provided it will be inferred from the anchor date.
NOTE: If the IntervalSchedule
anchor_date
or timezone
is provided in a
DST-observing timezone, then the schedule will adjust itself appropriately.
Intervals greater than 24 hours will follow DST conventions, while intervals
of less than 24 hours will follow UTC intervals. For example, an hourly
schedule will fire every UTC hour, even across DST boundaries. When clocks
are set back, this will result in two runs that appear to both be
scheduled for 1am local time, even though they are an hour apart in UTC
time. For longer intervals, like a daily schedule, the interval schedule
will adjust for DST boundaries so that the clock-hour remains constant. This
means that a daily schedule that always fires at 9am will observe DST and
continue to fire at 9am in the local time zone.
Args: interval (datetime.timedelta): an interval to schedule on. anchor_date (DateTime, optional): an anchor date to schedule increments against; if not provided, the current timestamp will be used. timezone (str, optional): a valid timezone string.
Whether or not the deployment schedule is active.
Whether or not the deployment is paused.
A list of schedules for the deployment.
Overrides to apply to the base infrastructure block at runtime.
Parameters for flow runs scheduled by the deployment.
A list of tags for the deployment
["tag-1", "tag-2"]
The work queue for the deployment. If no work queue is set, work will not be scheduled.
The last time the deployment was polled for status updates.
The parameter schema of the flow, including defaults.
The path to the working directory for the workflow, relative to remote storage or an absolute path.
Pull steps for cloning and running this deployment.
The path to the entrypoint for the workflow, relative to the path
.
The block document defining storage used for this flow.
The block document defining infrastructure to use for flow runs.
Optional information about the creator of this deployment.
Optional information about the updater of this deployment.
The name of the deployment's work pool.
Whether the deployment is ready to run flows. Enumeration of deployment statuses.
READY
, NOT_READY
Whether or not the deployment should enforce the parameter schema.