justabill
my-deployment
for a flow with the name `my-flow`:
prefect deploy --name my-flow/my-deployment
This is especially useful when you have several flows with deployments that have the same name.
You can also now use environment variables in deployment steps. You can access environment variables during the pull
action at runtime or during the build
and push
actions when running prefect deploy
. For example, you can now use the following syntax to set an image tag of a Dockerized build by loading an environment variable during the build
action:
yaml
build:
- prefect_docker.deployments.steps.build_docker_image:
requires: prefect-docker>0.1.0
image_name: my-image/orion
tag: '{{ $CUSTOM_TAG }}'
But wait, there's more! but wait theres more
When there are multiple deployments with the same name, the prefect deploy
command now prompts you to choose which one to deploy:
For example, if you have the following `prefect.yaml`:
yaml
deployments:
- name: "default"
entrypoint: "flows/hello.py:hello"
- name: "default"
entrypoint: "flows/hello.py:hello_parallel"
running prefect deploy -n default
will now prompt you to choose which flow to create a deployment for.
The Prefect Dashboard - your heads up display š š
The response to the experimental Prefect dashboard was so enthusiastic that we've made it generally available as the default landing page in the Prefect UI. The dashboard provides an overview of all Prefect activity, surfaces the urgent information, and provides the context to understand that information. With the dashboard, you can:
⢠Confirm that all flows run in the past 24 hours behaved as expected
⢠Identify a flow run that recently failed and jump directly to its page
⢠See a work pool that is unhealthy and the work that is impacted
See the release notes for more information.