Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Workflows for a custom Configuration Automation provider

Log in to subscribe to topics and get notified when content changes.

Workflows for a custom Configuration Automation provider

Workflows are optional depending on the requirements of the new configuration automation provider.

For example, Puppet does not use workflows; instead, the Puppet Master pulls the changes from the instance. Chef, however, uses the following workflows to pull changes.
Table 1. Workflows
Workflow Description
Push CI Change to Chef Server Pushes the configuration automation change to the Chef server.
Push Chef Changes By Node Definition Pushes configuration automation changes triggered by a node definition change.

If the new configuration automation provider requires workflows, register the workflows in Configuration Automation Provider form, and make sure to implement the getPushWorkflowName() and getWorkflowVariables(String workflowName, GlideRecord record) method in the change manager script.