github jamf/terraform-provider-jamfplatform v1.10.0

one hour ago

Highlights

  • Built against Jamf Pro 11.34.0. Jamf Pro 11.34.0 changed how three things behave, and the provider now adapts to each (#588).
  • New registry guide, "Versioning, deprecations and supported versions": a minor release can contain a breaking change, the 90-day deprecation window, what an older Jamf Pro tenant gets, and release cadence (#589).

Upgrade notes

  • Deprecated, removal after 2027-02-15:
    • jamfplatform_pro_policy: maintenance.fix_disk_permissions.
    • jamfplatform_pro_user_initiated_enrollment_settings: sign_quickadd_package and developer_certificate. Jamf's release notes list QuickAdd package signing for removal, estimated November 2026.
  • On Jamf Pro 11.34.0 or later, these now fail at terraform plan instead of at apply with an "inconsistent result" error:
    • maintenance.fix_disk_permissions = true
    • sign_quickadd_package = true without a developer_certificate

Fixes

  • Smart groups accept Patch Reporting: <title> criteria on Jamf Pro 11.34.0 or later. Older tenants still use the fallback (#588).
  • Data source acceptance test no longer depends on blueprint component list order.

Docs

  • New versioning-and-support guide. The importing guide gains a section on refused profiles (#589).
  • Contributor style guide split into contributing/ by concern; the quarterly endpoint audit is retired.

What's Changed

  • build(deps): Bump golang.org/x/text from 0.43.0 to 0.44.0 by @dependabot[bot] in #586
  • fix(pro): adapt to Jamf Pro 11.34 wire changes by @neilmartin83 in #588
  • docs: split the style guide by concern and publish the versioning policy by @neilmartin83 in #589
  • test: stop asserting supported_os on the first blueprint component by @neilmartin83 in #590

Full Changelog: v1.9.0...v1.10.0

Don't miss a new terraform-provider-jamfplatform release

NewReleases is sending notifications on new releases.