@Marvin I want to self-host Prefect on Kubernetes (AWS EKS). I don’t have to have a Prefect Cloud account for running flows on Kubernetes, right? I didn’t understand how to create a work pool or configure the worker when I use OSS Prefect. The docs has an example with Prefect Cloud.

Hi! When I run the example code after successfully logged in my prefect cloud (prefect version == 2.0b9), I got the error : prefect.exceptions.PrefectHTTPStatusError: Client error '422 Unprocessable Entity' for url 'https://api-beta.prefect.io/api/accounts/f68f7059-5eec-4e71-acc8-d7f351373e43/workspaces/ada6556d-d542-4378-9b90-b5647a4dd404/flow_runs/'. How can I solve this?

@Marvin How to trigger a flow instantly via REST api in Prefect 3

Hi everyone quite new to prefect and testing something out but I’m stuck,. I want to use

Deployment.build_from_flow

, it works when I put this in the same directory of the

flows

But what I want is the following:

- deployments:
   -- deployments.py (file with all my deployments)
- flows:
   -- flow_a.py
   -- flow_b.py

When I generate the deployments I get:

ValueError: '..../updates/flows/flow_a.py' is not in the subpath of '.../updates/deployments' OR one path is relative and the other is absolute.

It has to do with this line

entry_path = Path(flow_file).absolute().relative_to(Path(".").absolute())

-> it does not look like I can edit this “path” Anyone has done this before? Is this even possible?

@Marvin what is the simplest way to setup slack notifications on job failures?

Hi all, is there any way to disable tasks in the UI when I run a flow manually? I’m migrating flows from azkaban to prefect, and this is smth azk supports. Would be nice if prefect could do the same thing. The only way I can see rn to accomplish this would be to put case blocks in my code and add a parameter for each task to disable the task. This feels a bit overcomplicated though. Any help is welcome!

Does prefect have a drag-and-drop-based UI,? I want to use it for network operators. They can’t code.

@Marvin How do I run the same subflow concurrently for items in a list, passing the items in as an argument to the subflow

@Marvin I used a terraform module to start my ecs worker and I’m getting these worker logs.

6/22/2023, 2:21:26 PM GMT+1	raise PrefectHTTPStatusError.from_httpx_error(exc) from exc.__cause__	dd7a2b4d0c864a29a45c7fb3be8e12e0	prefect-worker-dev
6/22/2023, 2:21:26 PM GMT+1	prefect.exceptions.PrefectHTTPStatusError: Client error '401 Unauthorized' for url '<https://api.prefect.cloud/api/accounts/df07584b-fc84-43cb-a012-4a733392bcb7/workspaces/aebc2199-ddcd-430f-b7f1-de9c172d3892/work_pools/my-ecs-pool>'	dd7a2b4d0c864a29a45c7fb3be8e12e0	prefect-worker-dev
6/22/2023, 2:21:26 PM GMT+1	Response: {'detail': 'Invalid authentication credentials'}	dd7a2b4d0c864a29a45c7fb3be8e12e0	prefect-worker-dev
6/22/2023, 2:21:26 PM GMT+1	For more information check: <https://httpstatuses.com/401>	dd7a2b4d0c864a29a45c7fb3be8e12e0	prefect-worker-dev
6/22/2023, 2:21:26 PM GMT+1	Worker 'ECSWorker b98f1928-6596-4a06-83f1-84188da6d966' started!	dd7a2b4d0c864a29a45c7fb3be8e12e0	prefect-worker-dev

Hello, I'm trying to deploy prefect agents on an on prem environment, but I get a

prefect.exceptions.PrefectHTTPStatusError: Client error '403 Forbidden' for url '<https://api.prefect.cloud/api/accounts/xxxxxxxx/workspaces/xxxxx/work_queues/name/dev-prem-wq>'

I tried changing the api keys (service account) / giving ownership to the agent on the workspace, but nothing worked so far. I tried deploying the agents on the cloud on a kubernetes cluster and it works just fine, but when I try to do the same thing on our on prem environment, it returns me this error. Can I have some insights please ? Thanks