Hello all We have been working with flyte for some time and have been looking into setting the cache_version for tasks automatically. Depending on a change in any of the python files that go into a task then the cache_version is changed We have solved it ourselves by extending the decorator and it's working. My question, is this a usecase that you could see flyte supporting in the long term/have planned?

@nutritious-match-70820 there have been discussions in the past about a similar use case but not prioritized yet AFAIK.

We have solved it ourselves by extending the decorator and it's working.

Very curious to learn about this! cc @high-accountant-32689

could you elaborate a bit more on what you mean by

a change in any of the python files that go into a task

? do you mean any file that’s loaded? so even if a.py isn’t change but it imports something from b.py, and b.py is changed, then the task in a gets an updated cache version?

I lifted the decorator into a repo here https://github.com/AntonBjornNilsson/simplistic_flyte_auto_cache/tree/main @thankful-minister-83577 Yes, even if a.py isn't changed but b.py is -> cache version will update