Call tasks with inputs from the cli

[AustinAbro321]

Is your feature request related to a problem? Please describe

I would like to be able to require inputs on my tasks and run those commands from the command line

Describe the solution you'd like

• Given I have a task that looks like build-pkg below
• When I run uds run build-pkg --input pkg=my_pkg
• Then the task is ran with the input

  - name: build-pkg
    description: build a package
    inputs:
      pkg:
        description: pkg to build
        required: true
    actions:
      - cmd: cd "${PKG}" &&  go build -o ../build/${PKG} .
        description: "build pkg"

[UncleGedd]

Adding some context to this issue because we very briefly had a --with flag that did what @AustinAbro321 is asking for:

Here's some more context: The --with flag was meant to be used for testing tasks with inputs from the CLI. This feature ended up being confusing for users so we'd like to remove it. We believe this will encourage better testing patterns because it forces users to test their inputs with actual tasks instead of through the CLI.

[zachariahmiller]

Note you can now call tasks with inputs that have a default variable set, however there is no way to set them yet from the cli. What this solution with eventually look like depends on how we bring the separately implemented "variables" and "inputs" concepts together. Nonetheless i think this is a duplicate of:

#136

This issue was here first, but the other issue was already on our radar. Please confirm if you agree @AustinAbro321