Skip to content

Conversation

ShreehariVaasishta
Copy link

@ShreehariVaasishta ShreehariVaasishta commented Oct 4, 2025

fixes #2626

Adds support for Argo Workflow Title & description.

uv run --no-sync example_flow.py --environment=uv --with retry argo-workflows create --max-workers 4 --workflow-title "Example Flow" --workflow-description "Description of `Example Flow`"

)
self.enable_heartbeat_daemon = enable_heartbeat_daemon
self.enable_error_msg_capture = enable_error_msg_capture
self.workflow_title = workflow_title
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

consider keeping the title as the current.project_flow_name or current.flow_name and description as the doc strring of the flow

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yep!

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pushed changes

title defaults to `current.project_flow_name`
description defaults to flow's docstring
@saikonen saikonen self-requested a review October 6, 2025 17:06
Comment on lines +230 to +241
@click.option(
"--workflow-title",
default=None,
type=str,
help="Custom title for the workflow displayed in Argo Workflows UI. Defaults to `project_flow_name`. Supports markdown formatting.",
)
@click.option(
"--workflow-description",
default=None,
type=str,
help="Custom description for the workflow displayed in Argo Workflows UI. Defaults to the flow's docstring if available. Supports markdown formatting and multi-line text.",
)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there an existing use-case for the CLI options for setting custom title/description that warrants adding these as well? Not opposed to adding this.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The markdown support does not seem to be working, unless there's something off with my argo setup?

  • markdown in custom title/description is not being formatted in Argo UI
  • multi-line descriptions are rendered as one-liners (e.g. multi-line docstring)

Copy link
Author

@ShreehariVaasishta ShreehariVaasishta Oct 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there an existing use-case for the CLI options for setting custom title/description that warrants adding these as well? Not opposed to adding this.

The CLI flags let users provide concise, meaningful titles and descriptions (e.g. ETL [Prod], ML Pipeline v2.3.1) without changing code or flow names. It’s fully optional and backward-compatible, just giving flexibility for UI readability and dynamic deployments.


The markdown support does not seem to be working, unless there's something off with my argo setup?

  • markdown in custom title/description is not being formatted in Argo UI
  • multi-line descriptions are rendered as one-liners (e.g. multi-line docstring)

Verified working with Argo Workflows v3.6+ - headers, bold/italic, and multi-line formatting render correctly. Older UI versions may flatten multi-line text.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support "Title and Description" in Argo Workflows
3 participants