@Marvin How should i set auth string on prefect client? I want run deploy function to send script for be run on worker

@Marvin How to add dependencies between steps? like, i have a "main_flow". this should run "extract_flow" , "load_flow" and "transform_flow" (these are calling separate tasks). how to make them depend on each other and have correct lineage?

Hi,all After upgrading of Prefect 2 to 3, "run-graph" always say "This flow run did not generate any task or subflow runs" at a "Runs" pane with Deployment on Kubernetes Worker. Somehow but when I execute same flow at other workload, it works. why? woker "run-graph" show: Local Execution. does not show: Kubernetes Worker

@Marvin I want to use an ECS Push Workpool with 3.0. Help me understand the key differences between 2.0 and 3.0 with regards to how things will be structured in ECS

@Marvin how can I permanently remove a flow and deployment that fails to delete from the ui?

Hi All, im trying to serve the prefect ui behind a reverse proxy (traefik) running in k8s, at a subpath: dev.get-clarity.io/prefect/ however i dont seem to be able to configure the ui-settings, which i see when inspecting the webpage that requests to grab ui-settings are not being forwarded to the correct prefect service. its going to

<http://dev.get-clarity.io/ui-settings|dev.get-clarity.io/ui-settings>

rather than

<http://dev.get-clarity.io/prefect/ui-settings|dev.get-clarity.io/prefect/ui-settings>

can anyone offer advice on configuration of prefect server to enable access to the ui at a subpath?

Is this heartbeat configuration only applicable to Prefect cloud setups? https://docs.prefect.io/orchestration/concepts/services.html#heartbeat-configuration I have a (expected) long running job on a Prefect server setup trying to not have the zombie killer terminate the job:

No heartbeat detected from the remote task; marking the run as failed.

@Marvin how to handle sigterm to cleanup resources inside a prefect flow

Hello everyone! I use aws for my work. On my MacOS laptop .aws contains configuration files that are responsible for accessing my work cloud. I want to test prefect with another aws account but I'm afraid something might go wrong. As far as I understand, Prefect uses boto3, and boto3 will take configs from the default path. How to distinguish between a working aws profile and a home one, and what is the most important thing how to say about this to Prefect?

Hello, if anyone is using prefect on a SLURM cluster, I am interested in connecting to learn about the experience.