Legacy: Using change management with Puppet By default, the system allows changes to Puppet configurations only as part of a controlled change management process. With change management, users cannot directly edit Puppet records such as node definitions or the relationships between CIs and node definitions. For all changes to Puppet resources, the requesting user's manager must approve the request. If the user record does not have a value in the Manager field, the request is approved automatically. When a user requests a change, each change management approver and the requesting user receive a notification. Additionally, the system populates the Assigned to field on the change request with the requesting user. This user receives a notification when the request is approved or rejected. Legacy: Modify a Puppet nodeChange management prevents Puppet users from directly editing the Configuration automation or Node definition fields on the CI form.Legacy: Modify a Puppet node definitionThe Checkout Draft related link on the Puppet Node Definitions form creates an editable draft copy of the record.Legacy: Request a change to Puppet using the service catalogA user can request a change to a Puppet node through the service catalog. Changes to nodes through the service catalog require the same change request and approvals as changes made through the CI form.Legacy: Disable change managementDisabling change management with the Chef, Puppet, or ServiceNow provider allows users to make and save changes on the definition forms and templates and the Configuration Automation section of the CI form.