I ve got a question RE deployments with `null` local storage

Question

Clint M · Answer

The path that get s hard coded in the deployment yaml file looks like my source code path I just tested changing it to the local path in my docker file oooohh I know I m not supposed to do that it event says it in the file but I got it to work running in a container in eks

Clint M · Answer

I really don t want to provide you with my aws creds

Clint M · Answer

so I m willing to live with this hack for now but my question is

Clint M · Answer

why in the hell do I need to give you my AWS creds when this works

Clint M · Answer

why don t you just let me run my code in the prefect agent i e I don t want it uploaded to s3

Clint M · Answer

here s the relevant bit I m talking about ``` DO NOT EDIT BELOW THIS LINE flow name etl manifest path null storage null path Users clint code github flowcast till prefect example lt bad entrypoint src prefect example flow py etl parameter openapi schema title Parameters type object properties required null definitions null```

Clint M · Answer

I tried setting it to a relative path like ` ` but the agent runs the code in some temp dir

Clint M · Answer

can you let me use a variable there so I don t have to munge the path as part of my script to build the deployment yaml

Clint M · Answer

here s the error when I tried to use ` `

Clint M · Answer

``` prefect agent 84c5c6cd64 2r8gz prefect agent FileNotFoundError Errno 2 No such file or directory tmp tmp1b7dnxlfprefect src prefect example flow py ```

Clint M · Answer

so if I just change that to the root of my code for the container everything works fine e g ` home app code`

Oscar Björhn · Answer

I believe they re working on an official solution for this shouldn t be far off Not sure if that answers your question Probably not slightly smiling face

Clint M · Answer

thanks Oscar it s always nice to know I m not just shouting into the void so thanks for the response slightly smiling face

Oscar Björhn · Answer

Haha no worries I m looking forward to being able to pack my flows into docker images myself although I settled on keeping them in blob storage for now While you wait for the official feature did you consider creating separate aws storages not sure of the right term never used aws solely for storing the prefect flows That way you wouldn t have to worry too much about giving away your credentials

Clint M · Answer

I can lock down the creds so that they only have access to the one s3 bucket so I m not overly concerned about uploading them to a 3rd party I just don t want to do that work for every new project env combination that want s to use prefect I m also just bothered by the fact that it seems like it s required when it shouldn t be let me worry about my own code on my own infra it feels like it breaks their hybrid model

Oscar Björhn · Answer

That s fair I ve got the impression that deployments were launched in kind of a minimum state It seems like they re working on a bunch of new options for how you build package flows etc Just gotta watch out for those release notes slightly smiling face