broker/set-pipeline¶
Pipeline applied when a broker creates machines
When the broker creates machines, it assigns a pipeline to start during the join process. This will determine the operational path that the new machine follows.
This value sets the pipeline that will started when the machine is crated. Typically, the pipeline includes key configuration information and additional tasks to be injected during the configuration process.
Objects that Reference broker/set-pipeline¶
- profiles resource-proxmox-cloud in Cloud Wrappers v4.15.1 as part of Params (declared)
- profiles resource-vsphere-cloud in Cloud Wrappers v4.15.1 as part of Params (declared)
- profiles resource-libvirt in Cloud Wrappers v4.15.1 as part of Params (declared)
- profiles universal-application-openshift-cluster in Openshift v4.15.3 as part of Params (declared)
- profiles universal-application-vault-cluster in HashiCorp Tools v4.15.0 as part of Params (declared)
- profiles universal-application-drp-server-cluster in Universal Workflow Content v4.15.5 as part of Params (declared)
- profiles universal-application-base-cluster in Universal Workflow Content v4.15.5 as part of Params (declared)
- profiles universal-application-batch-environment-cluster in Universal Workflow Content v4.15.5 as part of Params (declared)
- profiles universal-application-multi-site-manager-demo-cluster in Universal Workflow Content v4.15.5 as part of Params (declared)
- profiles universal-application-context-worker-cluster in Universal Workflow Content v4.15.5 as part of Params (declared)
- profiles universal-application-dev-cluster-test in Dev Library v4.15.1 as part of Params (declared)
Objects used by broker/set-pipeline¶
Not used in current content packs