https://prefect.io logo
m

Mitch

07/17/2023, 7:56 PM
Hey team - it seems like workers do not support storage blocks as I received the error:
Copy code
Flow run UUID('XXXX') was created from deployment 'YYYYY' which is configured with a storage block. Workers currently only support local storage. Please use an agent to execute this flow run.
Is there going to be support for s3 or github in the workers?
b

Bianca Hoch

07/17/2023, 8:03 PM
Hi Mitch, with workers you can use s3 and github storage. It's just accomplished a bit differently compared to using agents + storage blocks. You'll define what storage you're using in the
pull
step of your prefect.yaml (which is part of the new
prefect deploy
experience).
m

Mitch

07/18/2023, 8:35 PM
Got it. I'll give it a try but it makes the migration a little more difficult
Could you also describe how to create a worker role and assign it to the worker? Right now I am a little confused as I seem to be able to give a worker a non-worker role, however the docs say I should be unable to do so.
Also, does the flow need to be deployed via the file or just have the file within the same directory as the flow?
b

Bianca Hoch

07/26/2023, 1:42 PM
Could you also describe how to create a worker role and assign it to the worker?
Hmmm. I believe the role is assigned to the service account that is used to spin up the worker. Are you using service accounts? Or are you using your own api key and user profile?
Also, does the flow need to be deployed via the file or just have the file within the same directory as the flow?
From what I understand, the best practice here is to have the prefect.yaml in the root of your directory.
And you'd point to the flow entry point by providing a path to the flow's file
m

Mitch

07/26/2023, 1:54 PM
I think we are going to end up just using an agent instead