https://flyte.org
Join Slack
another question from a while back: is there no longer a way to fetch the workflow version at runtim...
# flytekit
f
another question from a while back: is there no longer a way to fetch the workflow version at runtime anymore? this is useful say for setting a default cache version
f
Is it during registration?
f
execution time ideally
right now we manually set during docker build as an env var
f
Aah as an env car
Haha autocorrect- but yes envvar- I think this is fair and platform will expose this
Car
f
car
😉
actually yes, to your point it should be at registraion
to bascially
Copy code
@task(
  cache=True,
  cache_version=<workflow version>
)
f
Hmm registration- can you write up an issue of how you would like it to be consummable
f
no opinion on that at all 🙂 just want it to be consummable
used to be
Copy code
@task(
  cache=True,
  cache_version=os.env["FLYTE_WORKFLOW_VERSION"]
)
but this would be fine as well
Copy code
@task(
  cache=True,
  cache_version=flytekit.current_context().workflow_version
)
you want me to create an issue?
f
I think it won't be current context, but serialization context
Please file
h
don't want to hijack this thread, but being able to use the workflow version to set task metadata makes serializing non-cached tasks easier. we can use the workflow version as the dataset version for the reservation system.
165 Views
Open in Slack
PreviousNext
Powered by

Flyte

Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Powered by