Evan Sadler
08/22/2022, 6:16 PMNiels Bantilan
08/22/2022, 6:27 PMEvan Sadler
08/22/2022, 6:27 PMNiels Bantilan
08/22/2022, 6:33 PMFlyteRemote
depends on the config
argument.
Config.auto()
will do this to try and automatically find the config file, but you can use Config.for_sandbox()
for a flytectl sandbox
cluster and Config.for_endpoint()
for a specific endpoint identified via dnsfor_sandbox
will work for a flytectl demo
-started clusterEduardo Apolinario (eapolinario)
08/22/2022, 6:35 PMEvan Sadler
08/22/2022, 6:38 PMNiels Bantilan
08/22/2022, 6:46 PMFlyte inherently does this, the question is what surfacing the information looks like and will be pretty straight forward to investigateyes! we’ve been trying to figure out what kinds of utility functions to provide… for example, if we had:
remote = FlyteRemote(...)
remote.fetch_executions_with_output_type(sklearn.base.BaseEstimator)
would get all executions with sklearn models as outputs.
If you could articulate your different use cases, we’d love to figure out what those utility functions would be!Evan Sadler
08/22/2022, 6:48 PMremote.fetch_execution
with a task, but I can’t figure out how to look at individual tasks within a workflow.Niels Bantilan
08/22/2022, 9:30 PMexecution = remote.fetch_execution(...)
# make sure all the nodes are synced
synced_execution = remote.sync(execution, sync_nodes=True)
# get the node execution inputs/outputs
synced_execution.node_executions["n1"].inputs
synced_execution.node_executions["n1"].outputs["model_file"]
https://docs.flyte.org/projects/flytekit/en/latest/design/control_plane.html#retrieving-inspecting-executions
The you can get all the node keys with
synced_execution.node_executions.keys()
I forget now how the node execution keys are named… but that should allow you to get input/output data from tasks / subworkflow executionsEvan Sadler
08/22/2022, 9:36 PM