rich-garden-69988
04/21/2022, 8:49 PMfrom 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()
rich-garden-69988
04/21/2022, 8:50 PMthankful-minister-83577
thankful-minister-83577
pyflyte run
experience it makes even less sense.thankful-minister-83577
thankful-minister-83577
thankful-minister-83577
thankful-minister-83577
flytectl
(or in the case of pyflyte run
just overridden at grpc call time)freezing-airport-6809
rich-garden-69988
04/21/2022, 11:17 PMrich-garden-69988
04/21/2022, 11:18 PMfreezing-airport-6809
rich-garden-69988
04/21/2022, 11:19 PMrich-garden-69988
04/21/2022, 11:23 PMrich-garden-69988
04/22/2022, 3:13 PMfreezing-airport-6809
rich-garden-69988
04/22/2022, 4:36 PMfrom flytekit.configuration.file import ConfigEntry, LegacyConfigEntry
ConfigEntry(LegacyConfigEntry("internal", "version")).read()
^ will this no longer workthankful-minister-83577
thankful-minister-83577
thankful-minister-83577
thankful-minister-83577
rich-garden-69988
04/22/2022, 6:31 PMthankful-minister-83577
rich-garden-69988
04/22/2022, 6:32 PMthankful-minister-83577
rich-garden-69988
04/22/2022, 6:32 PMrich-garden-69988
04/22/2022, 6:33 PMbut that is your own optionThis 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)
thankful-minister-83577
pyflyte package
and then flytectl register
it would not have been used, even though the config object was still in the code.rich-garden-69988
04/22/2022, 6:34 PMthankful-minister-83577
thankful-minister-83577
echoing-translator-95395
04/26/2022, 9:54 PM<http://flyte.lyft.com|flyte.lyft.com>
…? ( or is that on purpose ? )