Carlo
11/06/2020, 1:28 PM2020-11-06T07:56:19.166-05:00
Copy
containerDefinition.flow-container.command -> Given: ['/bin/sh', '-c', "python -c 'import prefect; prefect.environments.execution.load_and_run_flow()'"], Expected: ['/bin/sh', '-c', 'prefect execute flow-run']
containerDefinition.flow-container.command -> Given: ['/bin/sh', '-c', "python -c 'import prefect; prefect.environments.execution.load_and_run_flow()'"], Expected: ['/bin/sh', '-c', 'prefect execute flow-run']
ale
11/06/2020, 1:35 PMCarlo
11/06/2020, 1:38 PMale
11/06/2020, 1:39 PMCarlo
11/06/2020, 2:07 PM0.13.13
but the error still persists. Are you using s3 storage?ale
11/06/2020, 2:14 PMSpencer
11/06/2020, 2:16 PMflow-container
) is injected by Prefect itself.
https://github.com/PrefectHQ/prefect/blob/8563cbb4b0a9e5db99045fb46717cac6ba172af5/src/prefect/environments/execution/fargate/fargate_task.py#L227-L245prefect execute flow-run
would be used by the AgentCarlo
11/06/2020, 2:21 PMSpencer
11/06/2020, 2:21 PMCarlo
11/06/2020, 2:21 PMSpencer
11/06/2020, 2:22 PMCarlo
11/06/2020, 2:23 PMSpencer
11/06/2020, 2:28 PMtaskDefinition
and family
are typically the same. I think those values may be the same as the flow-run taskDefinition
that the Agent is creating. You can look in the AWS ECS console to see the existing taskDefinition
Carlo
11/06/2020, 2:28 PMSpencer
11/06/2020, 2:28 PMtaskDefinition
here is named the same as a flow's flow-run taskDefinition
would be by the Agent. This probably won't happen if you're not using enable_task_revisions
since you'll get a fairly unique name, otherwise you could have a flow has a name that would collide. ( https://github.com/PrefectHQ/prefect/blob/master/src/prefect/agent/fargate/agent.py#L478-L487 )Carlo
11/06/2020, 2:30 PMflow.name
fargateTaskEnvironment.family
fargateTaskEnvironment.taskDefinition
all set to the same value