Hey folks wave We are planning Prefect Server upgrade from 0

Question

Hey folks wave We are planning Prefect Server upgrade from 0 13 13 to 0 15 x We are thinking of doing a 3 stage upgrade from 0 13 13 to 0 13 19 then from 0 13 19 to 0 14 22 then from 0 14 22 to 0 15 x However we are wondering if we can skip the second stage and go directly from 0 13 19 to 0 15 x Any suggestions

Zanie · Answer

I would just take a look at the breaking changes in Prefect Core and let us know if you have any specific questions

Kevin Kho · Answer

I think so Environments are still in the code base if you use them My only advice is to go through the whole changelog and look for the breaking changes 0 15 5 specifically has one where if you are accessing the server from different machines you need to start it with the ` expose` flag

ale · Answer

Sorry < Zanie> and < Kevin Kho> I forgot to add the second question sweat smile We use Docker storage and flows are built using 0 13 13 Do you think we might encounter issues if we upgrade the Server but keep flows at 0 13 13

Kevin Kho · Answer

I think you very likely will

Zanie · Answer

We inject environment variables into the containers which can be an issue over major version changes

Zanie · Answer

Generally we try to be backwards compatible still there Most of those breaking changes are auth related and may not affect you since you re a Server user but I d definitely do a trial run first

ale · Answer

Ok so maybe we can upgrade server to 0 13 19 and keep flows on 0 13 13 ensure flows work as expected and then upgrade them to 0 13 19 upgrade server to 0 14 22 and keep flows on 0 13 19 ensure flows work as expected and then upgrade them to 0 14 22 upgrade server to 0 15 x and keep flows on 0 14 22 ensure flows work as expected and then upgrade them to same version of server Make sense

Kevin Kho · Answer

yeah you could try that

ale · Answer

Thanks raised hands

ale · Answer

Hey folks simple smile Just wanted to let you know that the upgrade of Prefect server to 0 13 19 is going well Flows are still using 0 13 13 but we will upgrade them soon we already planned to upgrade to 0 14 22 and then to 0 15 x in the next couple of weeks After upgrading Prefect server on 0 13 19 from Prefect UI we see CORE VERSION 0 13 18+109 G37135691E Is this normal

Kevin Kho · Answer

Did you edit the source code lol

ale · Answer

Nope sweat smile

Kevin Kho · Answer

Will check with the team

Kevin Kho · Answer

Looks like we may have released a version of server with a dirty version of core hotfixes

ale · Answer

We use the following image for Prefect UI `prefecthq ui core 0 13 19`

Kevin Kho · Answer

Checked with the team and this happens all the time

ale · Answer

Ok so I assume it should not be an issue right blush

Kevin Kho · Answer

Not at all

ale · Answer

Cool Thanks for your support < Kevin Kho> raised hands

ale · Answer

Hey folks simple smile Just wanted to let you know that we were able to complete the upgrade from 0 13 19 to 0 14 22 quite easily on both Prefect flows and Prefect Server UI Agent In 2 3 weeks we plan to upgrade to 0 15 x

Kevin Kho · Answer

oh nice i am more confident about 0 14 22 to 0 15 x just note the breaking changes in the changelog

ale · Answer

Yep will look into that before upgrading

ale · Answer

I have a question related to ECSRunConfig Let s say that we have a flow that uses this type of run config and we set the task definition ARN using a variable Something like ```ECSRun task definition=my var arn ``` When will my var arn be evaluated At registration time or when the agent picks up the flow to be executed I m asking this because based on when my var arn is evaluated I might need to adapt our deployment process

Kevin Kho · Answer

At registration but I learned today that `StartFlowRun` can take in a RunConfig you can override the RunConfig during run time

ale · Answer

So if I have something like ```my var arn = os environ ARN ``` The ARN env var must be known at registration time right

Kevin Kho · Answer

Yes

Zanie · Answer

The agent pulls the run config from the server and then deploys the task so it needs to be known at registration time Once the task is created your flow code is downloaded and executed there at that point some values can become dynamic and loaded from the env if you want

ale · Answer

Thanks < Kevin Kho> raised hands Always appreciate your support pray

ale · Answer

And thanks < Zanie> as well slightly smiling face

ale · Answer

< grandimk> this might interest you as well simple smile

grandimk · Answer

Yes we can leverage that option