Quick question about flyte remote. I have a workflow that produces a

FlyteDirectory

as final output. Via flyteconsole/API I get a reference to the object, like so:

o0:
  type:
    multi-part
  uri:
    <gs://flyte-bucket/data/q1/pjziwgu55i-n1-0/48f7d1af2f65a6ff4c03fac9191cbea9>

If I try to fetch that workflow via

FlyteRemote

I get a local path as output. It's empty though.

remote = FlyteRemote.from_config()
exec = remote.fetch_workflow_execution("abc")
print(exec.outputs)
// /tmp/flyte3eg_mcpz/control_plane_metadata/local_flytekit/6f2223e1c864f6d1e88c8dbad090f349

What is the purpose of this local path and is there a way to get the original output location via

FlyteRemote

?

@thankful-minister-83577 Soren hold tight for 2 weeks. We are updating Flyte remote. It currently eagerly loads

Cool, thanks!

inside the object, the

_remote_source

field (there might be a

remote_source

property) should have the original path.

Ah I didn't realize I can just call

download()

on the output being a

FlyteDirectory

! Thanks @thankful-minister-83577

Is the api change going to contain some breaking changes?

there will be some yeah, but hopefully not too bad. The whole FlyteRemote experience was never really dialed in we think. We recently revamped the configuration of flytekit as well which affects this as well.

looking fwd