v0.28.0

✨ Impact alerts now cover policy dependencies

Scripts, packages, printers, Dock items, directory bindings and disk encryption configurations have no scope of their own — but every policy referencing one delivers it to that policy's audience. Jamf Pro shows no alert for this; the provider now does, as a third impact-alert channel alongside the deployable and scopeable object alerts shipped in v0.27.0:

Warning: Impact alert — this script affects up to 3 of 4 computers (75%), via 56 policies

  with jamfplatform_pro_script.auto_update,
  on main.tf line 15, in resource "jamfplatform_pro_script" "auto_update":

Used by 56 enabled policies: Jamf Auto Update - Adobe Acrobat DC - Ongoing, ... and 48 more.
Also 9 disabled policies, delivering nothing until enabled: ... and 1 more.
Counted from their combined scope: 36 groups: All Managed (3), All Laptops (2), ... and 31 more.
Computers in more than one are counted once.

Not resolvable during plan; the true figure may be lower:
  · scope.limitations.network_segments (1) — network segments are matched against a device's network location when it checks in
  · policy exclusions (111) — exclusions apply per policy, so cannot be subtracted from a combined audience

Searched 295 policies. Policy usage and group membership are a plan-time snapshot and can change before apply.

📖 Impact alerts guide — policy dependency changes

What's Changed

• chore(deps): bump github.com/Jamf-Concepts/jamfplatform-go-sdk from 0.14.0 to 0.15.0 by @dependabot[bot] in #321
• chore: add @grahampugh as a code owner by @neilmartin83 in #306
• chore(payloadhelpers): use maps.Copy in alignPayloadContentOrder by @neilmartin83 in #323
• feat(impact): alert on policy dependency changes; default min_request_interval_ms to 0; bump SDK to v0.16.1 (Pro 11.31) by @neilmartin83 in #322

Full Changelog: v0.27.0...v0.28.0