Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Workflows for a custom Configuration Automation provider

Workflows for a custom Configuration Automation provider

Workflows are optional depending on the requirements of the 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.

This site is scheduled for a small content update on Monday, November 12th, between the hours of 4:00pm and 9:00pm Pacific Time (Nov 13 00:00 – 05:00 UTC). Acces to this site may be delayed during that time.