• Anna Geller

    Anna Geller

    3 months ago
    Hi everyone, in case you forgot about - the Fireside Chat starts now 🔥
  • Kevin Kho

    Kevin Kho

    3 months ago
    Hi everyone! We have launched a new Prefect Associate Certification (PAC) Course, which is a two day immersive training dedicated to increasing engineering proficiency with workflow orchestration tooling for the modern data stack. The next session will take place on July 28-29 in San Jose, CA. More details can be found here. This will be a good opportunity to get hands-on workflow orchestration training, as well as network with fellow data practitioners. Just let us know if you’re interested or have any questions 🙂
  • Zach Angell

    Zach Angell

    3 months ago
    👋 Hello Prefectionists - we’ve just released the
    2.0b7
    version of Prefect 2.0! Thank you all again for the continued feedback. Exciting updates in this release include • Fixes for running the Orion UI on Windows • Adding a color select in the Orion UI, enabling users to change their state color scheme • Added anonymous blocks, allowing Prefect to dynamically store blocks for you without cluttering your workspace • Performance enhancements • and more … !! As a result of ongoing upgrades to Blocks, the backend API in 2.0b7is incompatible with previous Orion client versions. After the upgrade, your data will remain intact, but you will need to upgrade to 2.0b7to continue using the Cloud 2.0 API. You can upgrade in just a few simple steps: • Install the latest Prefect 2.0 python package:
    pip install -U "prefect>=2.0b7"
    Restart any existing agent processes • If you are using an agent running on Kubernetes, update the Prefect image version to 2.0b7in your Kubernetes manifest and re-apply the deployment. • You don’t need to recreate any deployments or pause any schedules - stopping your agent process to perform an upgrade may result in some Late Runs, but those will be picked up once you restart your agent. We will release this new version to Cloud 2.0 in about an hour. We’ll let you know again once the :cloud2: upgrade is complete. Happy engineering!
  • Zach Angell

    Zach Angell

    3 months ago
    Cloud 2.0 has been updated. After upgrading your agent, everything should continue to work as normal.
  • Anna Geller

    Anna Geller

    2 months ago
    Hi everyone, We are currently in the holiday season 🏖️ and working intensely on the Perfect 2.0 GA release planned for this summer. Community Support may be slow and limited in scope this month (July 2022). You may contact our paid support at cs@prefect.io if you have some mission-critical issues. I will be available to answer any of your questions during Office Hours between 7 and 9 AM EST (see my Slack status for the current availability). You may post your question anytime, but we will get back to you when we are available. To make it easier to get help during Office Hours: • Check the docs and Discourse whether it already provides the information you need • Make it clear whether your question is about Prefect 2.0 or Prefect 1.0 • Specify the problem rather than the feature or solution you tried. Focusing on a problem allows discussing many ways to solve it rather than focusing on a single approach you may have tried so far. • Define your issue as precisely as you can: ◦ explain your use case/problem in the main message, ◦ in the thread🧵, provide as many details as possible about: ▪︎ your environment (Cloud or self-hosted, the output of
    prefect version
    in 2.0 and
    prefect diagnostics
    in 1.0, your agent/storage setup, etc.), ▪︎ at which stage you are in your Prefect adoption, ◦ and document all steps you have taken so far to solve the issue you are facing in the thread. Thanks for understanding, and huge thanks to all community members helping others during that time! We appreciate you ❤️
  • Anna Geller

    Anna Geller

    2 months ago
    Hi everyone, On Wednesday (2022-07-06), we will perform Cloud 2.0 maintenance starting at 3 pm EST. The planned maintenance window is 3-5 pm EST. We'll let you know once this is completed. Thanks and have a great weekend!
  • justabill

    justabill

    2 months ago
    🚨 Heads up Prefect Cloud 2.0 Beta :cloud2: users: Tomorrow's
    2.0b8
    release will include a breaking change to the interface between Prefect Cloud 2.0 and your agents. You will need to upgrade your agents to ensure that your deployments continue to run as scheduled. We will announce both when the release is available and when Cloud 2.0 has been updated to work with the new client 📣. This release will not impact Cloud 1.0. <!here>
  • Anna Geller

    Anna Geller

    2 months ago
    Hi everyone! Some quick updates: 1. We’ve just pushed a new Prefect 1.0 release. Please check the link below for details. Thanks to all contributors! 2. The maintenance window mentioned here will likely shift to Thursday (same time). We'll keep you posted about the details 3. As Bill mentioned above, there will be also a Prefect 2.0 release published tomorrow - we'll let you know what changed and what you need to do on your end to make your code compatible with the latest Prefect 2.0 version. Thanks and you'll hear from us again very soon 👋
  • Anna Geller

    Anna Geller

    2 months ago
    Hi all! A bit delayed but the maintenance of Cloud 2.0 :cloud2: will start in an hour. ⚙️ Also, we've just released Prefect
    2.0b8
    with some really cool features - @justabillwill tell you more about it soon. You can take it for a spin already:
    pip install -U "prefect>=2.0b8"
  • justabill

    justabill

    2 months ago
    👋 Hey Prefectionists! We're psyched to share our biggest Prefect 2.0 😛refect2: release yet -
    2.0b8
    ! It's full of exciting new features and refinements to existing concepts, including: Flow Run Retries 🔄 Flow run retries have been one of our most requested features, especially given how easy it is to run a flow as a "subflow" or "child flow" with Prefect 2.0. Flow run retries are configured just as task retries are - with the
    retries
    and
    retry_delay_seconds
    parameters. If both a task and its flow have retries configured, tasks within the flow will retry up to their specified task retry limit for each flow run. For example, if you have a flow configured with a limit of 2 retries (up to 3 total runs, including the initial attempt), and a task in the flow configured with 3 retries (up to 4 attempts per flow run, including the initial attempt). The task could run up to a total of 12 attempts, since task retry limits are reset after each flow run or flow run attempt. Notifications 📣 You can always visit the Prefect UI to get a comprehensive view of the state of all of your flows, but when something goes wrong with one of them, you need that information immediately. Notifications can alert you and your team when any flow enters any state you specify, with or without specific tags. To create a notification, go to the new Notifications page via the sidebar navigation and select “Create Notification.” Notifications are structured just as you would describe them to someone. For example, if I want to get a Slack message every time my daily-ETL flow fails, my notification will simply read:
    If a run of any flow with any tag enters a failed state, send a notification to Slack
    Currently, notifications can only be sent to a Slack webhook (or email addresses if you are using Prefect Cloud 2.0). Over time, notifications will support additional messaging services. Let us know which messaging services you’d like to send your notifications to! Flow packaging and deployment 📦 We've revisited our flow packaging and deployment UX, making it both more powerful and easier to use. DeploymentSpecs are now just Deployments. Most of the fields are unchanged, but there are a few differences: • The
    flow_storage
    field has been replaced with a
    packager
    field. • The
    flow_location
    ,
    flow_name
    , and
    flow
    parameters are now just
    flow
    . You can deploy a flow directly, or you can package it with the new
    packaging
    module. Packaging enables you to bundle a flow with its dependencies, including Python packages. Packaging produces a Package, the artifact that contains your flow and its dependencies, as well as a Manifest, a JSON description of the package and what is inside of it. There are several ways to create a package, with more to come. For instance, you can package your flow as a Docker image containing the flow and the runtime environment necessary to run it and register it with Docker. Alternatively, you could package your flow as a reference to the import path of a package stored directly in the Prefect Orion database. Learn more in the Deployment concept documentation. You can continue to use your existing DeploymentSpecs, but they are deprecated and will be removed in the coming weeks. Blocks 🧱 We've been working on Blocks behind the scenes for a while. Whether you know it or not, if you've used the past few releases, you've used them. Blocks enable you to securely store configuration with the Prefect Orion server and access it from your code later with just a simple reference. Think of Blocks as secure, UI-editable, type-checked environment variables. We're starting with just a few Blocks - mostly storage, but over time we’ll expand this pattern to include every tool and service in the growing modern data stack. You'll be able to set up access to your entire stack once in just a few minutes, then manage access forever without editing your code. Breaking Changes 🚨 This release removes the deprecated
    DaskTaskRunner
    :dask: and
    RayTaskRunner
    :ray: from the core library, breaking existing references to them. You can find them in their respective collections prefect-ray and prefect-dask. It also removes the previously deprecated restart policy for the
    KubernetesFlowRunnner
    . Most importantly, there are new breaking changes to the Deployments interface described below. Special thanks to @Cole Murray, @Oliver Mannion, @Steve Flitcroft, and Laerte Pereira for their contributions to this release!
    justabill
    1 replies
    Copy to Clipboard