At the moment a workflow.yaml defines a step like:
id: a
expression: step.js
configuration: <uuid>
But should configuration actually be credential?
- credential is more in line with app language so it makes sense for that to be a UUID
- configuration is part of a runtime workflow structure, an execution plan. The runtime doesn't know anything about credentials, per se
- I think it makes sense for
credential to be an optional UUID, resolved by the CLI, and configuration to be a plain object. And you can have both