Marcin Grzybowski
05/30/2022, 10:02 AMtaskB.run()
but then it's treated as a normal python function (so no logging, and no other prefect's magic is available for this taskB)
I managed to workaround this creating a Flow in a Task, something like this:
@task
def taskA(config: dict):
#...
with Flow() as flowB:
taskB()
#...
a = flow.runB()
it seems to work - i get logs for flowB and taskB, etc
I can visualize both flows using flow.visualize() - on two separate diagrams - but it's all right for me.
But is this a correct approach, or should I do this some other way?Anna Geller
05/30/2022, 10:35 AMMarcin Grzybowski
05/30/2022, 10:44 AMAnna Geller
05/30/2022, 11:35 AMDeploymentSpec
abstractionMarcin Grzybowski
05/30/2022, 11:39 AMAnna Geller
05/30/2022, 11:46 AMMarcin Grzybowski
05/30/2022, 12:36 PMAnna Geller
05/30/2022, 12:55 PMMarcin Grzybowski
05/30/2022, 12:55 PMAnna Geller
05/30/2022, 12:55 PMIf your reliability, security, or scaling needs are the same as or less than hosting Prefect 2.0 yourself, start with Cloud 2.0 in production.
Marcin Grzybowski
05/30/2022, 12:56 PM