Prefect is a workflow orchestration tool empowering developers to build, observe, and react to data pipelines
APACHE-2.0 License
Bot releases are visible (Hide)
Published by znicholasbrown about 2 years ago
Releases some bug fixes and minor enhancements. Check out the release notes for more info.
Published by zanieb about 2 years ago
This release includes some important bug fixes and minor enhancements. Check out the release notes for details.
Published by zanieb about 2 years ago
There are some exciting features in this release:
The list of changes is way to big to fit here! Check out the full release notes.
Published by bunchesofdonald about 2 years ago
Task.map
in #6513empirical_policy
to flow run update route in #6486Deployment
objects in #6505deployment build
to raise an informative error if two infrastructure configs are provided in #6504Published by zanieb about 2 years ago
Fixes an issue where deployment flow run's would fail if they did not specify a value for parameters that have a default value on the flow function. A few minor fixes are included as well, see the release notes for more details.
Published by zanieb about 2 years ago
See the release notes for details about what's new in this release.
Published by abrookins about 2 years ago
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.deployment.yaml
file are more atomic and explicitinfra_overrides
fieldNow, 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.
prefect flow-run ls
Full Changelog: https://github.com/PrefectHQ/prefect/compare/2.0.3...2.0.4
Published by bunchesofdonald about 2 years ago
This release contains a number of bug fixes and documentation improvements.
prefect-dbt
We've released prefect-dbt
- a collection of Prefect integrations for working with dbt in your Prefect flows. This collection has been built as part of a partnership with dbt Labs to ensure that it follows best practices for working with dbt.
.prefectignore
--manifest-only
flag of prefect deployment build
command to ensure that using this flag, the manifest gets generated, but the upload to a storage location is skipped.prefect deployment apply
command.Published by zanieb about 2 years ago
ReadNamespacedPodLogs
- #5979
PowershellTask
for running commands with Microsoft Powershell - #6035
azure-mgmt-datafactory
requirement to 'extras', instead of 'orchestration_extras' - #6018
polling_interval
in azure.datafactory.PipelineRun
- #6021
Published by bunchesofdonald about 2 years ago
This release implements a number of improvements and bug fixes in response to continued engagement by members of our community. Thanks, as always, to all who submitted ideas on how to make Prefect 2 even better.
.prefectignore files allow users to omit certain files or directories from their deployments. Similar to other .ignore files, the syntax supports pattern matching, so an entry of *.pyc
will ensure all .pyc files are ignored by the deployment call when uploading to remote storage. Prefect provides a default .prefectignore file, but users can customize it to their needs.
deployment build
CLI command.Published by zanieb about 2 years ago
The response to Prefect 2 has been overwhelming in the best way possible. Thank you to the many community members who tried it out and gave us feedback! Thanks in particular to the students at this week's Prefect Associate Certification Course (PACC) in San Jose for their thoughtful recommendations. This release is a compilation of enhancements and fixes that make for a more resilient, performant, and refined Prefect experience.
prefect deployment execute
command has been removed to avoid confusion between running a flow locally from a Python script and running it by an agent using prefect deployment run
scheduler
and flow-run-notifications
LoopServices have been made more resilientbase_path
deployment build
command now supports an optional output flag to customize the name of the deployment.yaml file, to better support projects with multiple flowsPublished by zanieb about 2 years ago
We're thrilled to announce that, with this release, Prefect 2.0 has exited its public beta! Hopefully, this release comes as no surprise. It is the culmination of nearly a year of building in public and incorporating your feedback. Prefect 2.0 is now the default version of the open source prefect
framework provided upon installation. We will continue enhancing Prefect 2.0 rapidly, but future breaking changes will be less frequent and more notice will be provided.
Prefect 2.0 documentation is now hosted at docs.prefect.io. Prefect 1.0 documentation is now hosted at docs-v1.prefect.io.
Flows written with Prefect 1.0 will require modifications to run with Prefect 2.0. If you're using Prefect 1.0, please see our guidance on Discourse for explicitly pinning your Prefect version in your package manager and Docker, so that you can make the transition to Prefect 2.0 when the time is right for you. See our migration page to learn more about upgrading.
We have shipped a lot of breaking changes to Prefect 2.0 over the past week. Most importantly, recent changes to deployments required that schedules for all previously created deployments be turned off. You can learn more about the changes via the deployments concept documentation, the tutorial, or the discourse guide.
Published by zanieb over 2 years ago
Published by zanieb over 2 years ago
ExtraArgs
on S3 result upload - #5887
Git
storage could not be serialized without a repo
- #5877
DbtCloudRunTask.__init__
- #5831
boto_kwargs
support to S3List
- #5907
DatabricksSubmitMultitaskRun
inputs such as access_control_list
- #5836
single_user_name
to Databricks NewCluster
- #5903
NewCluster
- #5949
git_source
argument to DatabricksSubmitMultitaskRun
- #5958
DbtShellTask
return type to match ShellTask
- #5872
Published by zanieb over 2 years ago
SftpUpload
and SftpDownload
#1234
AirbyteConnectionTask
- #5794
StartFlowRun
- #5795
json
instead of dict
for DatabricksSubmitMultitaskRun
- #5728
LocalResult
- #5724
data_security_mode
to Databricks cluster configuration. - #5778
Published by zanieb over 2 years ago
max_duration
timeout in wait_for_flow_run
task - #5669
EdgeAnnotation
types, e.g. map
- #5674
DockerAgent
on Windows - #5657
prefect run
parameters to include equals ("=") signs - #5716
HightouchRunSync
task - #5672
DbtCloudRunJob
task failing with nested input for additional_args - #5706"Published by zanieb over 2 years ago
retry_on
to allow tasks to retry on a subset of exception types - #5634
DateTimeParameter
- #5519
flow.run
within a flow definition context will raise a RuntimeError
- #5588
azureml-sdk
dependency has been moved from the azure
extra into azureml
- #5632
create_bucket
to GCSCopy
- #5618
FlowRunView
could fail to initialize when the backend has no state data - #5554
Published by zanieb over 2 years ago
Thanks to our many contributors!
.pipe
operator to prefect.Task
for functional chaining - #5507
VaultSecret
- #5412
self
as an argument - #5508
create_flow_run
task when mapping during a local flow run - #5443
entrypoint.sh
- #5490
prefect server start
- #5476
Glob
task to accept a string path - #5499
RunNamespacedJob
- #5514
include_generated_sql
option to CubeJSQueryTask
- #5471
Published by zanieb over 2 years ago
🎉
See the latest documentation and our release blog post.
Environment
s have been removed; use RunConfig
s instead. - #5072, docs
DockerAgent(docker_interface=...)
will now raise an exception if passed. - #4446
prefect.cloud.agent.auth_token
config key. - #5140
prefect.engine.executors
; use prefect.executors
instead. - #3798
Parameter
is not importable from prefect.core.tasks
anymore; use prefect.Parameter
instead.prefect.utilities.exceptions
; use prefect.exceptions
instead. - #4664
Client.login_to_tenant
has been renamed to Client.switch_tenant
.prefect register flow
command has been removed; use prefect register
instead. - #4256
prefect run flow
command has been removed; use prefect run
instead. - #4463
create-token
, revoke-token
, list-tokens
have been removed; use API keys instead. - #4643
prefect auth login
no longer accepts authentication tokens. - #5140
prefect auth purge-tokens
has been added to delete the Prefect-managed tokens directory. - #5140
log_to_cloud
setting is now ignored; use send_flow_run_logs
instead. - #4487
LocalDaskExecutor
to use new Python futures feature. - #5046
State.__sizeof__
implementation to include the size of its result for better scheduling. - #5304
DaskExecutor
. - #5443
Flow.visualize()
to allow change in orientation. - #5472
DatabricksGetJobID
to retreive Databricks job IDs with a given name. - #5438
AWSParametersManager
task to retrieve value from AWS Systems Manager Parameter Store. - #5439
SpacyNLP
task to support spacy
version >= 3.0. - #5358
exclude
parameter to SpacyNLP
task. - #5402
AWSSecretsManager
task to parse non key-value type secrets. - #5451
DatabricksRunNow
task to use the Databricks 2.1 jobs API. - #5395
ge_checkpoint
and checkpoint_kwargs
parameters to RunGreatExpectationsValidation
to allow runtime configuration of checkpoint runs. - #5404
BlobStorageUpload
task. - #5437
Neo4jRunCypherQueryTask
task for running Cypher queries against Neo4j databases. - #5418
DatabricksSubmitMultitaskRun
task to run Databricks jobs with multiple Databricks tasks. - #5395
prefect.flatten
for non-iterable upstreams, including exceptions and signals. - #4084
rm=True
is used as default, which deletes intermediate containers. - #5384
__all__
to declare Prefect's public API for Pyright. - #5293
sys.getsizeof
to restore support for PyPy. - #5390
Published by zanieb over 2 years ago
See the list of changes in the changelog.