Hey, congrats to your release!!! I'm struggling to update my KubernetesJob deployments. (Prefect 2.0 Cloud user, updated my agents, CLI and KubernetesJob images to 2.0.0-python3.9) I ran the following command

prefect deployment build ../flows/r_script_automation.py:r_script_automation --name retention_cohort_analysis_deployment -t k8s -sb gcs/gcs-prefect-stprage -i kubernetes-job

If I then run "prefect apply..." and "prefect run..:", the job gets created, however it fails with:

Flow could not be retrieved from deployment.
FileNotFoundError: [Errno 2] No such file or directory: '/home/andreas/github/r_automation/flows/r_script_automation.py'

Note, that the directory /home/andreas.... is my local flow location, where I created the deployment from. It seems that somehow the job is not downloading the flow from GCS? My GCS storage block configuration is correct (I guess), because all my subprocess-flows work - only the KubernetesJobs have this problem. Any tips for me? 🙂

so you run the command

prefect deployment build

in the

/home/andreas

directory?

I ran it in the /home/andreas/github/r_script_automation/deployments directory.

So I assume your directory is like this:

r_automation
├── deployments
└── flows

Yes

I suggest that you run the command under the directory

r_automation

. The command will look like this:

prefect deployment build flows/r_script_automation.py:r_script_automation --name retention_cohort_analysis_deployment -t k8s -sb gcs/gcs-prefect-stprage -i kubernetes-job

See if that works

Oh... It works, awesome. Thanks for this very short-term input 😄 Just for my understanding: Why did it work now?

I’m glad that is works. Yes that’s correct. It is because when you run:

prefect deployment build

at the directory

r_automation

, there will be a manifest file created at the

r_automation

directory. When building your deployment and uploading your flow files to storage, the manifest file serves as the root of the directory that is uploaded — everything in its directory and recursively down will be stored in the storage of your choosing. More information about manifest.

Ah ok this is amazing! One final question: What happens, if I don't specify a storage-block during build command?

It will be stored in the local file system by default. You can find out more about storage here.

Ok, thanks. I've seen that, however was a little confused coming from the beta. Thanks again, everything clear, everything works again and the GA changes are very well appreciated. 👍

Yeah, we knew that it was confusing so we tried to make changes so that the concept of storage less confusing. I’m happy that it is clear now. Let me know if you have other questions in the future

Andreas it’s helpful to hear where you’re seeing friction in the process. It’s very new! I’m making some notes to revise those docs with more guidance. Cheers.