Workflows must be defined in terms of a particular type of UnitDef
they target, and an output of the workflow. By having a workflow
specilized to a particular type of unit, we avoid having to have
'uber workflows' that need to handle every possible type of unit,
which reduces the implementation complexity of a given workflow quite
considerably. In addition, the output type O is intended to provide
an opertunity for the workflow to output something more than just
effects. For example, a workflow could accumulate a set of logs, or
some reporting state - whatever - it doesnt matter.
Workflows define both setup (deploy) and teardown (detroy) workflow
Workflows must be defined in terms of a particular type of UnitDef they target, and an output of the workflow. By having a workflow specilized to a particular type of unit, we avoid having to have 'uber workflows' that need to handle every possible type of unit, which reduces the implementation complexity of a given workflow quite considerably. In addition, the output type
O
is intended to provide an opertunity for the workflow to output something more than just effects. For example, a workflow could accumulate a set of logs, or some reporting state - whatever - it doesnt matter.Workflows define both setup (deploy) and teardown (detroy) workflow