You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Notice how in the second execution of foo we override requests.
Currently the Task details view for the second task displays the original requests value.
Goal: What should the final outcome look like, ideally?
The Task Details view should be aware of resource overrides so as not to confuse users, since not having them there gives the false impression that those are not being applied, when in reality they are.
Propose: Link/Inline OR Additional context
The Task Details view for a given task execution should introspect the workflow closure to find which resources are being overridden (if any) and apply that transformation before rendering them.
Are you sure this issue hasn't been raised already?
Yes
Have you read the Code of Conduct?
Yes
The text was updated successfully, but these errors were encountered:
Based on Flyte Issue #4543, the Task Details tab in flyteconsole does not currently reflect resource overrides applied using with_overrides. This can lead to confusion as users might think the overrides are not being applied when they actually are.
Would you like more detail on how to address this issue or further explanation on the current behavior and potential fixes?
Motivation: Why do you think this is important?
The Task Details tab in flyteconsole is not aware of resource overridden in a task, e.g.:
Notice how in the second execution of
foo
we overriderequests
.Currently the Task details view for the second task displays the original
requests
value.Goal: What should the final outcome look like, ideally?
The Task Details view should be aware of resource overrides so as not to confuse users, since not having them there gives the false impression that those are not being applied, when in reality they are.
Propose: Link/Inline OR Additional context
The Task Details view for a given task execution should introspect the workflow closure to find which resources are being overridden (if any) and apply that transformation before rendering them.
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: