Executing Workflows using the CLI
Executing Workflows using the CLI
1.
To execute a workflow, use the execute command from within the context of the
selected workflow. If the workflow takes no parameters, it will simply execute:
dory:maintenance workflow-000> execute
hello world!
2.
If the workflow takes parameters, the context will become a captive context in
which parameters must be specified:
dory:maintenance workflow-000> execute
dory:maintenance workflow-000 execute (uncommitted)> get
type = (unset)
overwrite = (unset)
3.
Any attempt to commit the execution of the workflow without first setting the
requisite parameters will result in an explicit failure:
dory:maintenance workflow-000 execute (uncommitted)> commit
error: cannot execute workflow without setting property "type"
4.
To execute the workflow, set the specified parameters, and then use the commit
command:
dory:maintenance workflow-000 execute (uncommitted)> set type=system
type = system
dory:maintenance workflow-000 execute (uncommitted)> set overwrite=true
overwrite = true
dory:maintenance workflow-000 execute (uncommitted)> commit
5.
If the workflow has specified steps, those steps will be displayed via the CLI, e.
g.:
dory:maintenance workflow-000 execute (uncommitted)> commit
Checking for existing worksheet ... done
Finding disks of specified type ... done
Creating worksheet ... done
Auditing Workflows using the CLI
All workflows have a checksum property computed by the system. This checksum is the SHA-
256 digest of the workflow content. To determine if a workflow has changed, compare the
workflow checksum against its previous checksum.
Maintenance Workflows 609
To Next Page
Need help?
General
