I was using the following code before can explain use case i

Question

I was using the following code before can explain use case if helpful and was wondering if there is an alternative with the recent config changes My current code prior to 0 32 ```from flytekit configuration import internal internal VERSION get ``` Potential new way after 0 32 ```from flytekit configuration file import ConfigEntry LegacyConfigEntry ConfigEntry LegacyConfigEntry internal version read ```

Greg Gydush · Answer

Is this the correct way I should be getting workflow version

Yee · Answer

background on this this setting is actually something we ve been trying to get away from for a while in the past we used to run the compilation step of turning python code into flyte tasks and workflows from within the container image itself

Yee · Answer

we have moved away from that because we feel users typically don t care for that they d rather just run the compilation step from within their working environment like locally on their laptops especially with the new `pyflyte run` experience it makes even less sense

Yee · Answer

this setting was a way that we could inject the version of the task workflow basically the git sha into the image itself we did this by providing a special build script that added this tag

Yee · Answer

basically the version here is supposed to correspond to the version that these flyte entities will be registered to the Flyte backend with

Yee · Answer

which means this is not really necessary at all at compile time only when you send those objects to Admin do you need to provide the version

Yee · Answer

so in the new experience this is what we do we just put in this which is replaced by `flytectl` or in the case of `pyflyte run` just overridden at

Ketan (kumare3) · Answer

< Greg Gydush> why do you want to get the version in the code

Greg Gydush · Answer

I see appreciate the thorough background explanation

Greg Gydush · Answer

< Ketan kumare3 > I actually used that version to automatically set cache version for all tasks in a given workflow We like having cache tied to workflow version overridable by environment variable

Ketan (kumare3) · Answer

so you want basically every new version of git sha to be a new cache version

Greg Gydush · Answer

It s a little more complicated than that but kind of

Greg Gydush · Answer

We use more than git sha to register e g image hash different strategy for fast registration

Greg Gydush · Answer

Is what I suggested okay Or no I can also reach into our logic for naming to come up with the sha image hash myself rather than grab from current registered workflow

Ketan (kumare3) · Answer

what is your suggestion i did not catch it

Greg Gydush · Answer

```from flytekit configuration file import ConfigEntry LegacyConfigEntry ConfigEntry LegacyConfigEntry internal version read ``` ^ will this no longer work

Yee · Answer

what do you mean

Yee · Answer

that should continue to work for a while yes but that is your own option

Yee · Answer

right we removed that a while back

Yee · Answer

but my question is so long as you re making your own option why not just read from an env var where you need it instead of routing the logic through flytekit config code

Greg Gydush · Answer

FLYTE INTERNAL VERSION was something that flytekit provided On versions before lt 0 32

Yee · Answer

it was something that flytekit used

Greg Gydush · Answer

Yes but you re saying it s gone now

Yee · Answer

more accurately it may have been used

Greg Gydush · Answer

It is not possible to get this now right

Greg Gydush · Answer

gt but that is your own option This was not my own option is what I m saying This was an internal variable that I d still like to use If I cannot I will come up with an alternative totally fine

Yee · Answer

even on older versions if you ran `pyflyte package` and then `flytectl register` it would not have been used even though the config object was still in the code

Greg Gydush · Answer

I think we re just out of date < jeev> maybe we should change registration I ll look at this closer later today or next week

Yee · Answer

yeah if possible use an alternative

Yee · Answer

happy to hop on a call as well

austin · Answer

lt is that typos in the OSS version They contain references to `` or is that on purpose