v0.29.0-rc.4
Preparing for the Platform API GA
This pre-release targets the GA gateway. Every configuration written against the public beta needs changes, so please read the migration guide before upgrading:
π Preparing for the Platform API GA
The Platform API is still moving ahead of GA. That guide is provisional and may change without notice.
β οΈ Breaking changes
- 31 constructs were removed β 4 resources, 10 data sources, 3 list resources and 14 MDM command actions β because the endpoints behind them were unpublished. A workspace still holding one of the removed resources in state cannot produce a plan of any kind, including
plan -destroy, and the error reads like a Terraform bug. It is not. Remove the state entries withterraform state rm; the guide lists every affected type and the exact commands. base_urlmust change tohttps://{region}.api.jamfcloud.com, in the same change as the provider upgrade. The beta host is not supported on this version, and the GA host is not supported on earlier ones.- Beta API integration credentials are revoked at GA and cannot be migrated. They still work until then, including against the GA host β so this release can be adopted now, and the credential swap deferred to GA.
target_device_grouponjamfplatform_cbengine_benchmarkis replaced bytarget_device_groups. State migrates automatically; only the configuration needs editing.
At GA you will also register a replacement integration and, for most configurations, swap tenant_id for environment_id β mandatory if you manage blueprints or compliance benchmarks, whose permissions cannot be granted to a tenant-scoped integration. Nothing to do before then.
Installing
Terraform never resolves to a pre-release, so the version must be named exactly β ~> 0.29 and an unconstrained required_providers block both resolve to v0.28.1, which is bound to the retired beta gateway:
terraform {
required_providers {
jamfplatform = {
source = "Jamf-Concepts/jamfplatform"
version = "0.29.0-rc.4"
}
}
}Then terraform init -upgrade. A stable v0.29.0 follows shortly after GA; relax the constraint once it is out.
Also in this release
Jamf Security Cloud (custom DNS, ZTNA gateways and access policies, device groups, UEM Connect), Jamf AI Governance policies, environment_id scope, and proxy support via custom_headers. Built against Jamf Pro 11.31.0 and Classic API 11.28.0. All additive β see the guide's "Additions since v0.28.1", and the full commit log below.