Composite (JSON) Parameter?
Is it possible to evaluate a pipeline parameter that is itself a JSON document? I am finding a number of use cases for this, especially when using sub-pipelines and you need the input parameters to be pre-defined. It would clutter up a complex sub-p...