Jamf-Concepts/terraform-provider-jamfplatform v0.27.0

on GitHub

✨ Plan-time impact alerts

terraform plan now reports how many computers or mobile devices each scope or payload change will reach. Off by default:

provider "jamfplatform" {
  impact_alerts = true
}

Warning: Impact alert — this policy will be scoped to 47 of 312 computers (15%)

  with jamfplatform_pro_policy.security_baseline,
  on main.tf line 12, in resource "jamfplatform_pro_policy" "security_baseline":

Counted from 2 groups: All Managed Clients (44), Lab Macs (5).
Less 1 group excluded: Contractors (2).

• Advisory only. Never blocks a plan; an unreadable tenant gives one notice, not an error.
• 14 resources across policies, profiles, apps, ebooks, restricted software, patch policies, blueprints, benchmarks, classes and groups.
• Appears in terraform plan -json for advanced CI/CD workflow parsing/handling.

📖 Impact alerts guide

What's Changed

• chore(deps): bump github.com/hashicorp/terraform-plugin-log from 0.10.0 to 0.11.0 by @dependabot[bot] in #317
• chore(deps): bump github.com/Jamf-Concepts/jamfplatform-go-sdk from 0.13.0 to 0.14.0 by @dependabot[bot] in #318
• fix(payloadhelpers): tolerate Jamf Pro reordering PayloadContent entries by @macnotes in #320
• feat: plan-time impact alerts — device counts for scope changes by @neilmartin83 in #319

Full Changelog: v0.26.2...v0.27.0