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

Flyte

Hi!

Is there a way to get current image FQN (in case of a remote execution) from within a task? Specifically I would be interested in having that information in `PythonTask.pre_execute()` , so `user_params: ExecutionParameters` would also be available if that helps.

so no, not at this time, but this is something i’m pretty sure we can add

there’s a <https://github.com/flyteorg/flyte/issues/2490|related issue> for improving the sematics around that object

could you elaborate on the use-case a bit please?

you can always inject the name of the image, into the image itself if you need, as an environment variable.

in fact we used to do this… but it ended up being error prone and complicated so we worked around it

<@U03C1MJQ892> would love to understand the usecase. and also file an issue.
I think you can do this today, by adding the image as an environment variable. We did not want rely on Flyte internal vars

Thanks for the quick response <@UNR3C6Y4T> <@UNZB4NW3S>!

The usecase is that I am working on a `flytekit` `dask` plugin at the moment (very similar to <https://github.com/flyteorg/flyte/issues/427l|this Flyte issue>). I thought it might be nice if the `dask` cluster spins up its scheduler and worker nodes with the same image as the one that the Flyte task is running on (in the remote execution case).

As a side note, if we things are working, we would also like to upstream our changes and contribute the plugin to the `flytekit` repository. I've currently based my work on the new (and experimental) <https://kubernetes.dask.org/en/latest/operator.html|dask operator>.

Fantastic tbh, this would be best accomplished using a backend plugin

And for operators the plugins are easy to implement 

Also will allow to make the UX great and keep complexity of the plugin in flytekit minimal

<@U03C1MJQ892> Your link to the <https://github.com/flyteorg/flyte/issues/427l|similar Flyte issue> seems to be broken. Can you send the link again?

Ok, <@UNZB4NW3S> I'll look into the backend plugin, don't have a time estimate yet though (especially as we have a working `flytekit` plugin, which is only a few lines of code) :thumbsup:

<@U03BGLXSWMT> Sorry for that, this should be the link: <https://github.com/flyteorg/flyte/issues/427>

<@U03C1MJQ892> that is perfect. We can help with the backend plugin. But if you have a flytekit plugin, and are open to sharing it, we would love to TAL at it