argoproj / argoproj/argo-workflows

UI: URL parameter prefilling does not work on WorkflowTemplate and ClusterWorkflowTemplate pages

Open
#15,566 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
Go
Stars
17k
Forks
3.7k
Avg merge
1d 20h
Merged PRs (30d)
138

Description

# Summary

PR #13922 (from #12124) added the ability to prefill workflow parameters via URL query params when submitting workflows. However, this does not work on the `WorkflowTemplate` and `ClusterWorkflowTemplate` detail pages. The useEffect hooks in those pages overwrite the URL when updating the sidePanel state, stripping parameters[...] query params before the SubmitWorkflowPanel can read them.

## Use Cases

When deep-linking from external systems (e.g. alerting, runbooks) to submit a workflow from a template with prefilled parameters, the URL might look like:

`/workflow-templates/ns/my-template?sidePanel=submit¶meters[foo]=bar&entrypoint=my-entry&labels=env=prod`

Currently, navigating to this URL causes the parameters to be silently dropped, and the submit form opens with empty/default values.

## Expected Behavior

URL query params (parameters[...], entrypoint, labels) should be preserved and used to prefill the submit form on WorkflowTemplate and ClusterWorkflowTemplate detail pages, consistent with how it works for workflows.

## Actual Behavior

The parameters[...], entrypoint, and labels query params are stripped from the URL before the SubmitWorkflowPanel reads them, so the form always opens with default values.

---

**Message from the maintainers**:

Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.

Contributor guide

Open the contributing guide

Research direction

Start with the WorkflowTemplate and ClusterWorkflowTemplate detail pages, focusing on the useEffect hooks that update sidePanel state, then compare their URL handling with the workflow pages. Verify the SubmitWorkflowPanel still receives parameters[...], entrypoint, and labels from the URL and that these values prefill the form.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.