As it stands there is validation which forces you to supply casper_admin_privileges when certain permissions are set.
When making accounts, you get looping plans with changes to add casper_admin_privileges as they're not returned in the XML from Jamf. Example:
`<?xml version="1.0" ?>
505TF-JL-FULLTEST-1falsemicky mouseexampleEmailthing@domain.comexampleEmailthing@domain.com********************EnabledtrueFull AccessCustomCreate ScriptsRead ScriptsUpdate ScriptsDelete ScriptsCreate Directory BindingsRead Directory BindingsUpdate Directory BindingsDelete Directory BindingsCreate PrintersRead PrintersUpdate PrintersDelete PrintersCreate Dock ItemsRead Dock ItemsUpdate Dock ItemsDelete Dock ItemsCreate PackagesRead PackagesUpdate PackagesDelete PackagesCreate CategoriesRead CategoriesUpdate CategoriesDelete CategoriesRead SSO SettingsUpdate User-Initiated EnrollmentFlush Policy Logs`
We either need to amend this logic to auto supply the casper privs or omit them from state in all cases. One to discuss.
As it stands there is validation which forces you to supply casper_admin_privileges when certain permissions are set.
When making accounts, you get looping plans with changes to add casper_admin_privileges as they're not returned in the XML from Jamf. Example:
`<?xml version="1.0" ?>