Plugin Default Behavior Update about flyte

[kumare3]

I do not agree with this bug, the idea of task types is that we want to allow users define arbitrary client side task types (show them up in the UI) but the behavior of these tasks should be to actually run in a container.
But, I do agree with one part, that we should have better messaging when we defaulted the task type. Maybe for task execution events, we can show the TaskType of the task and the ExecutionTaskType?

[kumare3]

@EngHabu, wdyt?

[EngHabu]

I agree the real bug is the seemingly transparent/implicit behavior of the system.
I like the idea of showing/exposing the plugin ID somewhere.

We also, separately, talked about pinning plugins/plugin versions in the workflow closure and somehow deal with forced upgrades/ plugin changes... might be worth opening that discussion in the same veins...

[kumare3]

That is interesting, but should we close this issue and open a more appropriate issue?