DAB syntax for for_each task inputs is cumbersome

[ianepreston]

Describe the issue

The syntax for an array of inputs to a for_each task in DABs is a string formatted to be escaped into a json array rather than a native yaml array

Configuration

This is just a syntax challenge, so I'll just focus on the components that make this annoying for our use case

resources:
  jobs:
    tasks:
       - task_key: "many_inputs_task"
          for_each_task:
            inputs: "[\"input_1\",\"input_2\",\"input_n\"]"

Steps to reproduce the behavior

N/A

Expected Behavior

It would be nice to use yaml arrays to supply multiple inputs:

resources:
  jobs:
    tasks:
       - task_key: "many_inputs_task"
          for_each_task:
            inputs:
              - "input_1"
              - "input_2"
              - "input_n"

Actual Behavior

DABs doesn't accept that syntax or a few other variations we tried

Is this a regression?

No

Debug Logs

NA

[C0dingMast3r]

There is a slightly different way to do it that is cleaner. @ianepreston

Here is how I put inputs:

inputs: '[
                      {
                        "input1":"76",
                        "input1.1":"value"
                        },
                        {
                        "input2":"apple",
                        "input2.2":"valu123"
                        }
                      ]'