Hi, for prefect 2.0b4, how can I add a json file as parameter in a deployment?

If you mean a file name of a JSON file, then you could configure it as a string - parameters are validated with pydantic and must be JSON serializable - example:

from prefect import flow, task


@task
def do_something_with_path(path: str):
    filename = f"{path}/some_data.txt"
    data = "Hello world from Prefect 2.0!"
    with open(filename, "w") as file:
        file.write(data)
    return filename


@flow
def parametrized_flow_with_path(path: str):
    do_something_with_path(path)


if __name__ == "__main__":
    parametrized_flow_with_path(path_val)

then DeploymentSpec:

DeploymentSpec(
    flow=parametrized_flow_with_path,
    name="staging",
    schedule=IntervalSchedule(interval=timedelta(days=1)),
    parameters={"path": "/your/path"},
    tags=["local"],
)

Ik cool. Looks like I was on the right path:)

on the right "path" indeed 😄

This path is an absolute path based on the storage?

Based on the execution layer specified on the flow runner, e.g. if you started an agent and used SubprocessFlowRunner, then the flow run will be deployed as a subprocess on that agent and it would be best if this path is absolute to avoid any weird issues

In that sense it sounds like the smartest would be to parse the json within the deployment spec (but that's not possible in my case 🙁)?

as the Zen of Python says: explicit is better than implicit, and an absolute path will likely save you trouble down the road

That's what I do now indeed.

yes it does, you're right that there's no flow page, only a deployment page in 2.0 since the flow is supposed to be a dynamic concept and deployment spec is more a static concept defining static deployment-specific metadata that can be optionally overridden from the UI (on the roadmap)

In an earlier version I saw flow and deployments and flowruns and tasks on the landing page.

UI should show up as soon as you start Orion:

prefect orion start

Send you a DM with some screenshots

Your screenshots look fine, no issue there, that's the current state of the UI. Feel free to leave feedback if you want, I can forward that to the UI team

What I would expect in this case is to see one flow on the landing page with 13 deployments and only scheduled flow runs.

how is that different?

It seems the landing page doesn't show any data.

what do you mean by data in this context?

Data on the flows registered at the server (meaning there is a definition and id for the flow in the database)

what data would you expect there?

Could be related to my definitions. Let me investigate a bit

can you send a screenshot showing the AS-IS state and the TO-BE state in your view? hard to say what's exactly missing based on the description, maybe you can take a screenshot and draw over it what you mean?

Yep I know:) thanks. Trying to figure out how best to communicate this:)

you may also open a GitHub issue here with label v2 and UI - this would actually help a lot since it's easier to share feedback this way

I may need to create some simple example that's easy to replicate.

it's not about wasting time but more about shared understanding 🙂

I ran the UI at home on my Mac and all looked fine. Then trying out on a separate server at work this didn't work at all in b3. Now with b4 this is definitely better. Hence I need to make sure all is ok on my side:)

Great idea! Feel free to document how you do it and add it to your GitHub issue with your UI feedback

Tried to replicate this at home but messed up my network in the process:)

haha no rush, take your time

Actually, when you run the gui you can see in chrome dev tab still calls to 127.0.0.1. (Forgot to check that one) so no need to replicate elsewhere.