We've had a bit of a disconnect between this lib and cirrus for some time. Cirrus supports an array of process definitions in payloads under the process key, whereas stac-task only supports a single process definition object. The reason for a process array is to support workflow chaining.
This disconnect is only increasing, with cirrus v1 supporting only process arrays, for consistency and simplicity (only one right way to do things). We also chose to only support array values for process in swoop (and we had to add workarounds in each task we implemented because of this). Without an change to support process array values stac-task based tasks are not compatible with swoop and will no longer be compatible with cirrus out-of-the-box.
We've had a bit of a disconnect between this lib and cirrus for some time. Cirrus supports an array of process definitions in payloads under the
processkey, whereas stac-task only supports a single process definition object. The reason for a process array is to support workflow chaining.This disconnect is only increasing, with cirrus v1 supporting only
processarrays, for consistency and simplicity (only one right way to do things). We also chose to only support array values forprocessin swoop (and we had to add workarounds in each task we implemented because of this). Without an change to supportprocessarray values stac-task based tasks are not compatible with swoop and will no longer be compatible with cirrus out-of-the-box.