@Marvin i'm trying to deploy a flow using .serve() but after upgrading to 3.x i'm receiving this error:

prefect.deployments.runner.DeploymentApplyError: Error while applying deployment: Client error '422 Unprocessable Entity' for url '<http://localhost:4200/api/deployments/>'
Response: {'exception_message': 'Invalid request received.', 'exception_detail': [{'type': 'extra_forbidden', 'loc': ['body', 'infra_overrides'], 'msg': 'Extra inputs are not permitted', 'input': {}}, {'type': 'extra_forbidden', 'loc': ['body', 'manifest_path'], 'msg': 'Extra inputs are not permitted', 'input': None}

The error you're encountering,

422 Unprocessable Entity

, often occurs due to Prefect 3.x's stricter handling of deployment parameters. Specifically, the

infra_overrides

and

manifest_path

fields are not recognized in the context you're attempting to use them. Here are some key points to address this issue: 1. Work Pools and Job Variables: Prefect 3.x uses work pools and job variables for infrastructure configuration. Ensure that you are using the correct fields for your deployment. The fields like

infra_overrides

and

manifest_path

are not valid inputs in Prefect 3.x deployments. You should instead focus on using

job_variables

to customize infrastructure settings. 2. Deployment Method: Ensure you are using the correct deployment method. Prefect 3.x recommends using the

from_source

method for deployments, and you should configure your deployment using a

prefect.yaml

file or the Python deployment method. 3. Review Documentation: Review the Prefect 3.x deployment documentation to ensure you are following the updated practices for defining and deploying flows. 4. GitHub Issues: There are related issues on GitHub, such as this one, which discuss similar errors. These might provide additional insights or workarounds specific to your use case. 5. Common 3.x Gotchas: Prefect 3.x has several changes from 2.x, such as the replacement of agents with workers and the introduction of work pools. Make sure your deployment process aligns with these changes. You may need to refactor your deployment configuration to adhere to these new standards in Prefect 3.x. If you have specific configurations you need help translating, feel free to share them.

Make sure your prefect version between the server and the flow's environment match

how can i check that?

In both environments there's a

prefect version

command available

both are in 3.1.11

are you specifying

infra_overrides

in your code anywhere? if you did have the right versions and you were using that instead of the new alias (job_variables) then this might also happen

hm... i've found some infra_overrides parameters in some yamls of the project, that could be it, i'll investigate that, thanks

yep! you should be able to just replace all instances of that with

job_variables

directly

thanks for that!

Is it the same error?

yeah

how about

manifest_path

?

no, only on old files outside of the prefect.yaml

something is weird here

'manifest_path': None, 'storage_document_id': None, 'infrastructure_document_id': None,

all three of these are completely removed in 3.x, which makes me think you have a

Deployment.build_from_flow

or other some 2.x style deployment definition somewhere

this is how i'm trying to deploy my flow:

if __name__ == "__main__":
    metal_pipeline()
    metal_pipeline.serve(name="metal")