Closed grg1bbs closed 7 months ago
We will change this to work with patch1+. The reason I have named this "root_group" instead of "parent_group" is because if you have nested groups it does not refer to the parent group but rather the name of the root group. For example:
{
"NetworkDeviceGroup": {
"name": "Parent#Parent#Child1#NestedChild1",
"ndgtype": "Parent"
}
}
Addressed in v0.1.9 .
TF version = 1.6.6 ISE version = 3.2 patch 4
When using the 'ise_network_device_group' resource block to create a new Root Network Device Group, TF throws a Client Error due to "Resource Initialization Failed: Invalid JSON: Unrecognized field \"ndgtype\" (Class network.NetworkDeviceGroup), not marked as ignorable\n "
Suspect the resource has not been updated since the API was changed - https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwd24304
API documentation: https://developer.cisco.com/docs/identity-services-engine/latest/#!networkdevicegroup
TF output
TF code example:
API PUT call that results in a 201 Created
Additional comments Suggest renaming 'root_group' attribute to 'parent_group' as that is how it is named in ISE and NDGs can have multiple tiers of hierarchy