broker/set-workflow¶
Workflow that is started on machines after broker apply
When the broker creates machines, it assigns a workflow to start
during the join process. For cloud machines, this is typically
universal-start (default). For physical machines, this is typically universal-discover.
For Pipelines, this value must be one of the chained workflow states; consequently,
the typical values are universal-start and universal-discover.
Objects that Reference broker/set-workflow¶
- profiles resource-proxmox-cloud in Cloud Wrappers as part of Params (declared)
- profiles resource-libvirt in Cloud Wrappers as part of Params (declared)
- profiles resource-vsphere-cloud in Cloud Wrappers as part of Params (declared)
- profiles universal-application-backup-server in Backup and Recovery as part of Params (declared)
- profiles universal-application-dev-generate-load in Dev Library as part of Params (declared)
- templates cluster-provision.sh.tmpl in Core Task Library as part of Contents (used)
- templates terraform-tf.vars.tmpl in Core Task Library as part of Contents (used)
- tasks broker-pool-manipulate in Core Task Library as part of Templates.[0].Contents (used)
- tasks broker-context-manipulate in Core Task Library as part of Templates.[0].Contents (used)
- tasks cluster-restart-pipeline in Core Task Library as part of Templates.[0].Contents (used)
- profiles universal-application-drp-server-cluster in Universal Workflow Content as part of Params (declared)
- profiles universal-application-openshift-cluster in Openshift as part of Params (declared)
- tasks openshift-direct-pool-operations in Openshift as part of Templates.[0].Contents (used)
- tasks openshift-manage-in-process-machines in Openshift as part of Templates.[0].Contents (used)
Objects used by broker/set-workflow¶
Not used in current content packs