Does this PR only apply for Remote Storage blocks and not LocalFileSystem blocks? https://github.com/PrefectHQ/prefect/pull/6518

yes exactly, for local execution everything is on your computer so no need for blocks at all

We have an on-prem setup where the code is stored on a windows share in a mono-repo. Is there a convenient way to access sub-folders within the share for flow storage without creating blocks for every folder?

hmm I think you shouldn't have to worry about blocks at all when you leverage such local storage - those are likely displayed as anonymous blocks because they simply hold a reference to your flow path

when deploying the flow how do you reference storage?

when you create a deployment using local storage, you don't have to define any storage block at all, you can just do:

# DEFAULT STORAGE & INFRASTRUCTURE: locally stored flow code + Local Process; -a stands for --apply; no upload is happening
prefect deployment build -n prod -q prod -a flows/healthcheck.py:healthcheck
prefect deployment build -n prod -q prod -a flows/parametrized.py:parametrized
prefect deployment build -n prod -q prod -a flows/hello.py:hello

thanks, maybe i was overcomplicating our setup

Interesting, there is nothing specific to this but I would encourage you to open a GitHub issue if this doesn't work for you as expected on a Windows Server.

Ok, I think I’ve worked this out. You can explicitly set the path to the code location when building the deployment using the --path param or using the path variable in the build function (if using the python API). Now the anonymous block references “//servername/path/to/code/folder” and the entry point is something like “./flow.py:flow_name”

Great work!

It might help to add documentation under the build function of the Deployment class indicating that the path variable can be used to specify location of a locally stored flow as well. Currently it says this:

path: str = typer.Option(
        None,
        "--path",
        help="An optional path to specify a subdirectory of remote storage to upload to."

@Anna Geller Do you know why LocalFileStorage does not support relative paths like RemoteStorage?

because it's not a remote storage block and doesn't need to upload files - local storage assumes everything is local e.g. your laptop: your code is local, agent running locally, prefect installed locally, no need to upload anything to a remote location because the files are "in the computer" 😉

Maybe I’m missing a larger point. I understand the local nature of the block. I guess the question then is, why have a LocalFileStorage block at all if everything can be done strictly using local paths?

I'm AFK so can't check but don't treat local storage as block, ideally you shouldn't even have to use --path because you can specify the flow path in the build command i.e. the entrypoint