v0.32.0

⚠️ Action required: this provider has moved to the jamf namespace

v0.32.0 publishes as jamf/jamfplatform. Everything up to v0.31.2 published as
jamf-concepts/jamfplatform, and Terraform records the namespace in state alongside every
resource the provider manages, so editing source alone will not move a configuration across.

For each workspace and each state file holding jamfplatform resources, rewrite the state
first:

terraform state replace-provider jamf-concepts/jamfplatform jamf/jamfplatform

Then point source at the new namespace, leaving any version constraint as it is:

terraform {
  required_providers {
    jamfplatform = {
      source = "jamf/jamfplatform"
    }
  }
}

Then run terraform init.

OpenTofu works the same way, with tofu in place of terraform.

Full instructions, and the parts that are easy to get wrong:
Moving to the jamf namespace.

What stays the same

Nothing on the Jamf side changes. The same credentials, base_url, scope attribute, resources and
data sources apply on either side of the move.

Previous releases keep working. Everything from v0.12.1 to v0.31.2 is published under
jamf/jamfplatform as well, and the jamf-concepts/jamfplatform versions go on resolving, so
nothing breaks if you do nothing today. You can change namespace now and upgrade whenever you
like. New versions land only under jamf from v0.32.0 on.

The repository moved to
github.com/jamf/terraform-provider-jamfplatform.
Existing links and clone URLs redirect.

Also in this release

The migration warning that fired on every plan and apply is gone.

---

What's Changed

• chore: move the provider to the jamf namespace by Neil Martin (@neilmartin83) in #420

Full Changelog: v0.31.2...v0.32.0