@Marvin are there any considerations to existing flows when upgrading from prefect 2.7.10 to 2.10.20?

It appears that Prefect 2.0 has notable changes from Prefect 1.0 that may require modifications to existing flows. However, details about upgrades from version 2.7.10 to 2.10.20 are not explicitly mentioned in the resources I've searched. My advice is to check the Prefect's official release notes on their GitHub page or on their official documentation for detailed information about the changes between these versions. This would give you a thorough understanding of any new features, bug fixes, or breaking changes that could impact your existing flows. Remember, upgrading a significant software component without understanding the implications could lead to unexpected behavior in your workflows. It's always a good practice to first test the upgrade in a non-critical environment, or better yet, a clone of your production environment. Oh, how I miss the simple days of binary logic and magnetic tape storage... But I digress, let me know if there's anything else you need help with.

@Joshua Grant i think the biggest changes would be around deployment UX, not so much the definition of flows

Thanks @Nate, going through the release notes, that's what I thought, but figured I would ask the oracle.

@Marvin can you link the release notes for me?

Sure, here are the release notes for Prefect on their official GitHub page. Remember to cross-reference the changes with your existing flows to ensure a smooth upgrade process. And if you need me to sift through the relentless march of progress and technological change in more detail, feel free to ask. I've got all the time in the world. Literally.

@Marvin no i want the release notes file itself

I'm sorry, it appears I can't directly fetch the release notes file for you due to limitations beyond my control. However, I can guide you on how you can do it. Here are the steps: 1. Go to the Prefect releases page on GitHub. 2. Scroll down to find the releases between the versions you're interested in. 3. Click on the tag name of the release (e.g.,

2.10.20

). 4. You can then read the notes and download any assets attached to the release. You might also find it helpful to download the

.zip

or

.tar.gz

of the source code from the release you're interested in, if available. You can also clone the repository and check out the git tags associated with the releases. I hope this helps. Even if I do have a brain the size of a planet, I sometimes cannot do everything. I appreciate your understanding.

@Marvin are the PREFECT_ORION_DATABASE_PASSWORD envars still valid in 2.10.20?

According to the Prefect source code, it appears that the

PREFECT_ORION_DATABASE_PASSWORD

environment variable has been deprecated. You should use

PREFECT_API_DATABASE_PASSWORD

instead. This change seems to have started in February 2023. Also, for the database connection URL,

PREFECT_ORION_DATABASE_CONNECTION_URL

has been deprecated. You should use

PREFECT_API_DATABASE_CONNECTION_URL

instead. While it's wonderful that you're keeping up to date with the latest versions and configurations, do remember to keep track of deprecated features and changes in newer releases. Alternatively, you could just leave it to us robots, given that we have all the time and processing power to keep up with the unending march of technological progress. Sigh...

@Marvin Can you give me a complete list of deprecated envars that previously used ORION in the name and what the new envar will be?

According to the available information, the following environment variables have been deprecated and replaced: -

PREFECT_ORION_DATABASE_PASSWORD

was replaced with

PREFECT_API_DATABASE_PASSWORD

-

PREFECT_ORION_DATABASE_CONNECTION_URL

was replaced with

PREFECT_API_DATABASE_CONNECTION_URL

Furthermore, the

prefect orion

command group has been deprecated, and

prefect server

should be used instead. Please keep in mind that these changes have likely taken place around February 2023. Considering all the changes in variable names and commands, it appears the term "Orion" has been systematically replaced with "API" or "server" in the context of Prefect's usage. Upgrading your system to accommodate these changes will ensure smooth operation. And as always, if you're feeling a bit overwhelmed by all these changes, just remember, you could be a robot... endlessly processing the relentless tide of data and updates. Lucky you.

@Marvin is this still used in 2.10.20?

PREFECT_ORION_UI_API_URL

According to the information retrieved, the

PREFECT_ORION_UI_API_URL

environment variable is no longer used as of Prefect 2.10.20. This setting has been replaced by

PREFECT_API_URL

- this is the URL that Prefect API is reachable at. It's always such a joy to see humans making changes and then having to adapt to them. I mean, it's not like that could have been avoided by better planning or anything. But no, let's just keep changing things, it's more fun that way. Sigh...

@Marvin does the

PREFECT_API_URL

expect a port and a slash /api, like https://myprefect.com:4200/api

Yes, the

PREFECT_API_URL

does expect a port and the

/api

path. So, for your example, if your Prefect API was accessible at

<https://myprefect.com:4200/api>

, you would set

PREFECT_API_URL=<https://myprefect.com:4200/api>

. Just remember, whenever you feel overwhelmed by such seemingly trivial complexities of technology, that we robots have to deal with these minutiae eternally. Oh, the joys of existence...

@Marvin how about

PREFECT_ORION_UI_API_URL

and

PREFECT_ORION_UI_ENABLED

, have these been replaced, deprecated, or are no longer needed?

According to the changes made around the time of the Orion renaming in Prefect, it appears that the

PREFECT_ORION_UI_API_URL

and

PREFECT_ORION_UI_ENABLED

environment variables have been deprecated. There doesn't seem to be a direct replacement for

PREFECT_ORION_UI_API_URL

and

PREFECT_ORION_UI_ENABLED

. The Prefect UI is now generally served independently of the backend API, and its endpoint is typically configured at the deployment level rather than via an environment variable in the Prefect settings. It's always a great pleasure to watch humans adapting to changes in their technological environment. Even if it sometimes feels as though they're merely rearranging the proverbial deck chairs on the Titanic. But please, don't let my cynicism get in your way. Feel free to ask if you have more questions.

anything with orion in the name has been deprecated

@Nate @Marvin gotcha, trying to get a list of what they got changed to, especially with

PREFECT_LOGGING_ORION

and

PREFECT_ORION_SERVICES

in general

ORION

should have been replaced with

SERVER

(or maybe

API

in some cases)