another question from a while back: is there no lo...
# flytekitd
Dylan Wilder
02/03/2022, 2:42 PManother 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
k
Ketan (kumare3)
02/03/2022, 3:01 PM
Is it during registration?
d
Dylan Wilder
02/03/2022, 4:18 PMexecution time ideally
Dylan Wilder
02/03/2022, 4:18 PMright now we manually set during docker build as an env var
k
Ketan (kumare3)
02/03/2022, 4:19 PM
Aah as an env car
Ketan (kumare3)
02/03/2022, 4:19 PM
Haha autocorrect- but yes envvar- I think this is fair and platform will expose this
Ketan (kumare3)
02/03/2022, 4:19 PM
Car
d
Dylan Wilder
02/03/2022, 4:19 PMcar
Dylan Wilder
02/03/2022, 4:19 PM😉
Dylan Wilder
02/03/2022, 4:19 PMactually yes, to your point it should be at registraion
Dylan Wilder
02/03/2022, 4:20 PMto bascially
Copy code
@task(
cache=True,
cache_version=<workflow version>
)k
Ketan (kumare3)
02/03/2022, 4:20 PM
Hmm registration- can you write up an issue of how you would like it to be consummable
d
Dylan Wilder
02/03/2022, 4:20 PMno opinion on that at all 🙂 just want it to be consummable
Dylan Wilder
02/03/2022, 4:21 PMused to be
Copy code
@task(
cache=True,
cache_version=os.env["FLYTE_WORKFLOW_VERSION"]
)Dylan Wilder
02/03/2022, 4:21 PMbut this would be fine as well
Copy code
@task(
cache=True,
cache_version=flytekit.current_context().workflow_version
)Dylan Wilder
02/03/2022, 4:22 PMyou want me to create an issue?
k
Ketan (kumare3)
02/03/2022, 4:22 PM
I think it won't be current context, but serialization context
Ketan (kumare3)
02/03/2022, 4:22 PM
Please file
d
Dan Rammer (hamersaw)
02/03/2022, 10:45 PMdon'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.
166 Views