For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Previously in the Itential Platform, if a Golden Configuration with the same name already existed and you attempted to import a new one, you would get an error. This limitation is now removed in the UI, thereby enabling you to manage Golden Configs in Configuration Manager through a set of actions that will enhance how you handle the standard by which your devices should be configured.
Import Golden Configs
When importing Golden Configurations, certain characteristics and behaviors occur if you do not pass in an extra property with each tree. These include:
If the name is a duplicate, a unique index is used, such as GC Name (1)
If the name is not a duplicate, then the original name is used in the export, such as GC Name
The output file format is JSON. A download of the export file is shown in your browser. Once the download is complete, locate the export file in the downloads folder and perform an import.
Export file output JSON
Overwrite Golden Configs
When overwriting Golden Configurations, certain behaviors occur if you pass the overWrite: true property with each tree. These behaviors are as follows:
The entire Golden Configuration is replaced except for devices and task instances
Versions in the current Golden Configuration that do not exist in the imported Golden Configuration are deleted
Versions in the imported Golden Configuration that exist but are not available in the current Golden Configuration are added
Rename the file name directly in the error message by clicking on the name (for example, JSON to JSON Copy). Notice that the error message and the Overwrite button changes to Rename instead.
Click Rename. A success banner appears and the original JSON and the newly named JSON Copy file are displayed in the Collections window.
Success confirmation
Use the import API in Golden Configuration
This section provides backend developer information for importing, overwriting, and renaming Golden Configurations. Here are the parameters for calling the API:
1
{
2
"trees": [
3
{
4
"data": [{treeVersion1}, {treeVersion2}],
5
"overwrite": true
6
},
7
{
8
"data": [{treeVersion1}, {treeVersion2}],
9
"newName": "New GC Name"
10
},
11
{
12
"data": [{treeVersion1}, {treeVersion2}]
13
}
14
],
15
"options": {}
16
}
Each element in the trees array represents a Golden Configuration. Within each Golden Configuration, the data array represents each version that belongs to a Golden Configuration. For example, if a Golden Configuration has three versions, then the data array is going to have three objects inside of it for each version. Essentially, the payload is saying to import three Golden Configurations and each of those three Golden Configurations has two versions each.
To import a Golden Configuration, you can just pass in the import data and nothing else. It will:
Either import the tree normally, assuming it’s not a duplicate
Index the name if it is a duplicate in which a tree name already exists (for example, if a tree called IOS Tree already exists then it will import as IOS Tree (1))
Overwrite property
To overwrite for a Golden Configuration, you have to pass the overwrite: true property.
Renaming property
To rename a Golden Configuration, you have to pass in the newName property.