feat: Add ability to submit CronWorkflow from CLI

[simster7]

…. Closes #1963

Examples:

$ argo submit --from "CronWorkflow/hello-world"
Name:                hello-world-f6g7v
Namespace:           argo
ServiceAccount:      default
Status:              Pending
Created:             Thu Jan 16 12:03:45 -0800 (now)

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
• The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
• I have written unit and/or e2e tests for my change. PRs without these are unlike to be merged.
• Optional. I've added My organization is added to the README.
• I've signed the CLA and required builds are green.

[codecov]

Codecov Report

Merging #2003 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #2003   +/-   ##
======================================
  Coverage    11.7%   11.7%           
======================================
  Files          52      52           
  Lines       26313   26313           
======================================
  Hits         3081    3081           
  Misses      22837   22837           
  Partials      395     395

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ebeeac6...7a4236f. Read the comment docs.

[alexec]

I'd like to review this, but it is not on the project board, so it has not been prioritized :(

[simster7]

@alexec Added to the review board

[alexec]

@jessesuen is this high priority?

[simster7]

I think it should certainly be included with the next release

[simster7]

Waiting on #2048 and #2007 before continuing -- possibly merging only CronWorkflow submission and then opening a separate PR once #2007 is done.

[simster7]

Have scaled back this PR to only allow submission from CronWorkflow. Submission from WorkflowTemplate will be added in #2007. v1.Interface use will be introduced with #2114.

Ready for another review @alexec

[alexec]

Changes requested, including two moderately sized one.

You'll need to git merge master before you can merge.

[alexec]

used of back ticks makes for nice help:

submit a workflow

Usage:
  argo submit [FILE... | --from `kind/name] [flags]

Examples:
# Submit multiple workflows from files:

  argo submit my-wf.yaml

# Submit a single workflow from an existing resource

  argo submit --from cronwf/my-cron-wf


Flags:
      --dry-run                 modify the workflow on the client-side without creating it
      --entrypoint string       override entrypoint
      --from kind/name          Submit from an existing kind/name E.g., --from=cronwf/hello-world-cwf
      --generate-name string    override metadata.generateName
  -h, --help                    help for submit
      --instanceid string       submit with a specific controller's instance id label
  -l, --labels string           Comma separated labels to apply to the workflow. Will override previous values.
      --name string             override metadata.name
  -o, --output string           Output format. One of: name|json|yaml|wide
  -p, --parameter stringArray   pass an input parameter
  -f, --parameter-file string   pass a file containing all input parameters
      --priority int32          workflow priority
      --server-dry-run          send request to server with dry-run flag which will modify the workflow without creating it
      --serviceaccount string   run all pods in the workflow using specified serviceaccount
      --strict                  perform strict workflow validation (default true)
  -w, --wait                    wait for the workflow to complete
      --watch                   watch the workflow until it completes

done