Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Housekeeping] More readable names for task executions. #6028

Open
2 tasks done
dansola opened this issue Nov 19, 2024 · 1 comment
Open
2 tasks done

[Housekeeping] More readable names for task executions. #6028

dansola opened this issue Nov 19, 2024 · 1 comment
Labels
help wanted Extra attention is needed housekeeping Issues that help maintain flyte and keep it tech-debt free

Comments

@dansola
Copy link
Contributor

dansola commented Nov 19, 2024

Describe the issue

Flyteadmin makes task execution names that can be hard to read. For example, for a task named my_new_task with a path src.tasks.my_new_task, the task execution name will be srctasksmynewtask which is not that readable when this name is used in the UI. I would suggest we use my_new_task if possible as this would be consistent with task names when a workflow is executed.

What if we do not do this?

The UI will remain hard to read for individual task executions.

Related component(s)

No response

Are you sure this issue hasn't been raised already?

  • Yes

Have you read the Code of Conduct?

  • Yes
@dansola dansola added the housekeeping Issues that help maintain flyte and keep it tech-debt free label Nov 19, 2024
@wild-endeavor wild-endeavor added the help wanted Extra attention is needed label Nov 19, 2024
@wild-endeavor
Copy link
Contributor

wild-endeavor commented Nov 19, 2024

image (11)
image (10)
pictures from @dansola

these are determined by admin iirc so the change will need to be made there.

the second picture is what it should be.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed housekeeping Issues that help maintain flyte and keep it tech-debt free
Projects
None yet
Development

No branches or pull requests

2 participants