Open ecanault opened 2 weeks ago
Hi,
Perhaps a bug in configuration profiles regarding exclusions in scope?
scope
The provider accepts the following:
scope { all_computers = true all_jss_users = false building_ids = [] computer_group_ids = [] computer_ids = [] department_ids = [] jss_user_group_ids = [] jss_user_ids = [] }
This one is also accepted:
scope { all_computers = true all_jss_users = false building_ids = [] computer_group_ids = [] computer_ids = [] department_ids = [] jss_user_group_ids = [] jss_user_ids = [] exclusions { building_ids = [] computer_group_ids = [ 208, ] computer_ids = [] department_ids = [] directory_service_or_local_usernames = [] directory_service_usergroup_ids = [] ibeacon_ids = [] jss_user_group_ids = [] jss_user_ids = [] network_segment_ids = [] } }
But not this one:
scope { all_computers = true all_jss_users = false building_ids = [] computer_group_ids = [] computer_ids = [] department_ids = [] jss_user_group_ids = [] jss_user_ids = [] exclusions { building_ids = [] computer_group_ids = [] computer_ids = [] department_ids = [] directory_service_or_local_usernames = [] directory_service_usergroup_ids = [] ibeacon_ids = [] jss_user_group_ids = [] jss_user_ids = [] network_segment_ids = [] } }
It's OK to have computer_group_ids to be empty for main targets, but not in the exclusions.
computer_group_ids
exclusions
Thanks, Emmanuel
@ShocOne
Hi,
Perhaps a bug in configuration profiles regarding exclusions in
scope
?The provider accepts the following:
This one is also accepted:
But not this one:
It's OK to have
computer_group_ids
to be empty for main targets, but not in theexclusions
.Thanks, Emmanuel