Pre-requisites

• I have double-checked my configuration
• I have tested with the :latest image tag (i.e. quay.io/argoproj/workflow-controller:latest) and can confirm the issue still exists on :latest. If not, I have explained why, in detail, in my description below.
• I have searched existing issues and could not find a match for this bug
• I'd like to contribute the fix myself (see contributing guide)

What happened? What did you expect to happen?

Please see images attached.
Image 1 shows input parameters configuration where entry point is default while submitting the WF.
Image 2 shows input parameters listed twice where entry point is switched to main while submitting the WF.

Version(s)

v3.6.7

Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflow that uses private images.

metadata:
  name: sample-workflow
  namespace: argo-workflows
spec:
  templates:
    - name: main
      inputs:
        parameters:
          - name: parameter1
          - name: parameter2
      outputs: {}
      metadata: {}
      container:
        name: ""
        image: bitnami/kubectl:latest
        command:
          - /bin/bash
          - -c
        args:
          - >
            set -e

            sleep 3600
        resources: {}
  entrypoint: main
  arguments:
    parameters:
      - name: parameter1
        description: parameter1
      - name: parameter2
        default: "a"
        enum:
          - "a"
          - "b"
        description: parameter2