Description

FileTaskHandler should have the ability to get logs not only from the default executor, but from one configured on the task instance

Use case/motivation

With the introduction of multiple executors flow of the FileTaskHandler log reading of the running task was broken if the task was run by a non-default executor.

For example, usage of "LocalExecutor,KubernetesExecutor" leads to an inability of online logs reading in web interface.

I was able to overcome it with a custom executor workaround, but I belive that this would be a reasonable feature to expect with multiple executors.

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct