Simplified deployments
The deployment experience has been refined to remove extraneous artifacts and make configuration even easier. In particular:
- `prefect deployment build` no longer generates a `manifest.json` file. Instead, all of the relevant information is written to the `deployment.yaml` file.
- Values in the `deployment.yaml` file are more atomic and explicit
- Local file system blocks are no longer saved automatically
- Infrastructure block values can now be overwritten with the new `infra_overrides` field
Start custom flow runs from the UI
Now, from the deployment page, in addition to triggering an immediate flow run with default parameter arguments, you can also create a custom run. A custom run enables you to configure the run's parameter arguments, start time, name, and more, all while otherwise using the same deployment configuration. The deployment itself will be unchanged and continue to generate runs on its regular schedule.
Improvements and bug fixes
- Made timeout errors messages on state changes more intuitive
- Added debug level logs for task run rehydration
- Added basic CLI functionality to inspect Blocks; more to come
- Added support for filtering on state name to `prefect flow-run ls`
- Refined autogenerated database migration output
New Contributors
* hugolmn made their first contribution in https://github.com/PrefectHQ/prefect/pull/6275
**Full Changelog**: https://github.com/PrefectHQ/prefect/compare/2.0.3...2.0.4