Dynamic Golden Configuration

Dynamic GC Compliance & Remediation

Golden Configurations ("GC") are frequently managed through the UI for many operations; however, it was important that Itential extend this functionality to Studio (formerly Automation Studio) via exposed tasks as well. Previously, it was difficult to dynamically design Golden Configurations through tasks and APIs, but with two new APIs it has now become straightforward. With that being said, the following tasks have been implemented.

updateNodeConfig API

The updateNodeConfig task allows you to easily update the configuration of a node in a Golden Configuration ("GC") tree.

Example

{
  "treeId": "60ad5b4948555dc621052bd0",
  "treeVersion": "initial",
  "nodePath": "base/US-West",
  "data": {
      "template": "ntp server {{ntp_ip}}",
      "variables": {
          "ntp_ip": "192.15.32.146"
      }
  },
  "updateVariables": false
}

convertChangesToConfig API

The convertChangesToConfig task displays the remediation payload as a native configuration to preview the config that would be sent to the device for application.

Example

{
  "deviceType": "cisco-ios",
  "changes": [
      {
          "parents": [],
          "old": null,
          "new": "hostname IOS-Device1"
      }
  ]
}

Workflow Design

In order to do dynamic compliance and remediation you can start by:

1. Creating a Golden Config tree.
2. Updating the base node with a new configuration.
3. Adding devices to that node.
4. Running compliance on that node.
5. Fetching and looping over each compliance report and remediating it.
6. Deleting the GC Tree once all compliance/remediation is done.

You can reference the following automation to review the tasks that might be required to complete the dynamic compliance/remediation process. One primary difference would be that the updateNodeConfig would have dynamic information being passed in for the configuration parameter.