Terraform version = 1.6.6
ISE version = 3.2 p4
Provider version = 0.1.9
In testing Policy Set creation, it was unclear what the exact structure needs to look like for multiple nested children conditions. To check this, I manually created a basic Policy Set via the GUI, then used the 'terraform import ise_network_access_policy_set.' command to import the object into state.
Upon import, the 'terraform state show ' output shows only the id value.
Example output:
❯ tf state show ise_network_access_policy_set.ps_wired_mm
# ise_network_access_policy_set.ps_wired_mm:
resource "ise_network_access_policy_set" "ps_wired_mm" {
id = "0a38ed78-0d1f-4d77-8456-6668c59d0949"
}
Expected behaviour:
The state should import all of the attributes and values that were configured in ISE for this object. This same behaviour should be seen from all supported import actions.
Example Policy Set configuration from the GUI:
Example output from GET API call for the same Policy Set ID
Terraform version = 1.6.6 ISE version = 3.2 p4 Provider version = 0.1.9
In testing Policy Set creation, it was unclear what the exact structure needs to look like for multiple nested children conditions. To check this, I manually created a basic Policy Set via the GUI, then used the 'terraform import ise_network_access_policy_set. ' command to import the object into state.
Upon import, the 'terraform state show ' output shows only the id value.
Example output:
Example tfstate object:
Expected behaviour: The state should import all of the attributes and values that were configured in ISE for this object. This same behaviour should be seen from all supported import actions.
Example Policy Set configuration from the GUI:
Example output from GET API call for the same Policy Set ID