As there is no PUT/PATCH method for /api/cb/engine/v2/benchmarks the provider will force a replacement during an update.
This will cause the resource to be destroyed and created again. This in turn will remove and re-create all associated configuration profiles, policies, groups, EAs and scripts, deleting and re-installing them on all computers in scope.
Any subsequent changes that have been made to these assets (e.g editing one of these scripts/profiles/policies etc by click-ops or Jamf Pro/Classic API) will be lost as they are not managed by the provider, since it only deals with the Compliance Benchmark item itself. The CB engine is then responsible for any creation/deployment/removal of these objects in Jamf Pro.
As such, this is not something that can be fixed at the provider level until such a time when the API provides a PUT/PATCH method for Compliance Benchmarks.
As there is no PUT/PATCH method for
/api/cb/engine/v2/benchmarksthe provider will force a replacement during an update.This will cause the resource to be destroyed and created again. This in turn will remove and re-create all associated configuration profiles, policies, groups, EAs and scripts, deleting and re-installing them on all computers in scope.
Any subsequent changes that have been made to these assets (e.g editing one of these scripts/profiles/policies etc by click-ops or Jamf Pro/Classic API) will be lost as they are not managed by the provider, since it only deals with the Compliance Benchmark item itself. The CB engine is then responsible for any creation/deployment/removal of these objects in Jamf Pro.
As such, this is not something that can be fixed at the provider level until such a time when the API provides a PUT/PATCH method for Compliance Benchmarks.