Drop the netboot_server of override_default_settings in policy
The attribute netboot_server in override_default_settings in policy does not exist as a Jamf API strict.
I have therefore removed the relevant attribute.
Some objects in policy have different default values, corrected
When we run terraform plan against the policy, we may get differences every time.
resource "jamf_category" "category1" {
name = "category1"
priority = 9
}
resource "jamf_category" "category2" {
name = "category2"
priority = 9
}
resource "jamf_policy" "test" {
general {
name = "[terraform] Test Policy 1"
enabled = true
frequency = "Ongoing"
category {
id = jamf_category.category1.id
name = jamf_category.category1.name
}
network_limitations {}
override_default_settings {}
site {}
}
self_service {
self_service_category {
id = jamf_category.category1.id
}
self_service_category {
id = jamf_category.category2.id
}
self_service_icon {}
}
scope {}
reboot {}
}
The cause of this phenomenon is that the default values are different from those expected by this provider.
The response of Jamf API at this time is as follows
Description
Drop the netboot_server of override_default_settings in policy
The attribute netboot_server in override_default_settings in policy does not exist as a Jamf API strict. I have therefore removed the relevant attribute.
Ref: https://developer.jamf.com/jamf-pro/reference/findpoliciesbyid
Some objects in policy have different default values, corrected
When we run
terraform plan
against the policy, we may get differences every time.The cause of this phenomenon is that the default values are different from those expected by this provider. The response of Jamf API at this time is as follows
Therefore, to the best of my knowledge and influence, I have modified the default values of the
jamf_policy
resource.