Skip to content

Releases

Blueshift 1.8.0

Choose a tag to compare

@k1joshi k1joshi released this 18 Nov 16:21
184f41c

Blueshift 1.8.0 records which devices a migration has to reach and won't let you retire the original profile until the blueprint has reached them. It also adds Dry Run, Terraform export and migration reports, and it includes the fixes planned for 1.7.15, which won't be released separately.

New: devices are checked before you retire anything

  • Check Profile records which devices have the profile installed (from Jamf Pro inventory) and which devices its scope reaches. Blueshift does this automatically when you migrate.
  • Check Blueprint then checks each of those devices against the blueprint by serial number: Verified, Pending, Failed, Not covered, Original still installed, Inventory not updated, or New device. Results are saved, so they're still there after a relaunch.
  • Retiring the original is refused while any device is Not covered, Failed or Pending, and Blueshift names those devices. Migrations made before 1.8 keep the earlier count-based check.

New: Dry Run. Use the switch at the foot of the sidebar, or View ▸ Dry Run (⌥⌘D). Every write to Jamf is stopped. Jamf's API still checks each new blueprint ("Jamf would accept"), but nothing is created. Writes… lists everything Dry Run stopped.

New: Terraform export. Blueprints export as jamfplatform_blueprints_blueprint resources for jamf/jamfplatform 1.9 or later. You can export from the Create Blueprint sheet, for a batch, or for existing blueprints with import blocks. You can also save the raw API request as JSON.

New: reports. Export pre-migration and migration reports from the File menu, and per-profile device reports, as PDF, Excel or CSV. You can also select several blueprints and export one report or one Terraform file for all of them.

New: client secret expiry reminder. Enter the expiry date for your API client, and a banner on the Overview reminds you as the date approaches. If Jamf refuses a secret after that date, Blueshift reports it as expired.

Payload coverage (the planned 1.7.15 fixes)

  • Energy Saver, Time Server, Mobile Accounts and Accounts profiles no longer show as Wrapped. They're now sent as the type Blueprints accepts.
  • Extensible SSO converts to Blueprints' SSO declaration instead of showing as blocked.
  • New converters: accounts (CalDAV, CardDAV, Mail, LDAP, Exchange), DNS settings, IKEv2 VPN, content filter plug-in, and the macOS 26.4 and 27 declarations. Profiles that can't be converted safely are refused with the reason, instead of being sent as a wrapper that does nothing.
  • Settings the Blueprints API would silently drop are now kept as managed preferences, or listed so you know.
  • Blueshift ▸ Check for Updates…

Install: download Blueshift-1.8.0.dmg, open it and drag Blueshift to Applications, replacing the old copy. Your settings and migration records carry over. Requires macOS 14 or later. Signed by JAMF Software and notarised by Apple.

Build 1.8.0 (1). DMG SHA-256: 4c322db6bda9de19526634951d8e763ff79c96964161cba5d4f4d1c262bc69e9

Blueshift 1.7.14

Choose a tag to compare

@k1joshi k1joshi released this 11 Nov 17:17
184f41c

Blueshift 1.7.14 adds a second way to move a profile and makes retiring the original safer.

New: Keep as Installed. When you create a blueprint you can now choose how the profile moves:

  • Convert (the default) builds a new blueprint that sits beside the profile until you retire it.
  • Keep as Installed uses Apple's in-place takeover: devices that already have the profile keep it, with no reinstall and no gap, and the blueprint takes it over once deployed. Blueshift checks whether a profile can be adopted and tells you why if it can't. Try it on a test group first.

Safer retiring. Blueshift no longer lets you unscope, rename-and-unscope or delete the original profile until its blueprint is deployed and reporting on devices. Before retiring, it warns that on a large fleet Jamf Pro can keep retrying Remove Configuration Profile commands that devices refuse.

Fixes

  • Scrolling quickly through profiles no longer shows "Cannot convert this profile — cancelled".
  • Mobile profile links open the right page in Jamf Pro.
  • Computer attribution uses the Jamf Pro v4 inventory API (v1 was removed in Jamf Pro 11.36.0).
  • Bulk retire counts refused profiles correctly, and the migration record always points at the right blueprint.

Install: download Blueshift-1.7.14.dmg, open it and drag Blueshift to Applications, replacing the old copy. Your settings and migration records carry over. Requires macOS 14 or later. Signed by JAMF Software and notarised by Apple.

Build 1.7.14 (1). DMG SHA-256: b56003efcbe8e30d3ffb4b9ddb71589e8c8315826f506c3f71c4057db74c4766

Blueshift 1.7.11

Choose a tag to compare

@k1joshi k1joshi released this 23 Oct 19:01
242db50

First release of Blueshift as a Jamf Concepts app.

Blueshift migrates Jamf Pro configuration profiles to Jamf Blueprints. It gives every payload a verdict before anything is sent, carries the profile's scope across (and can build a smart group for what blueprint scope can't express), and helps you retire the original profile afterwards.

Install: download Blueshift-1.7.11.dmg, open it and drag Blueshift to Applications. Requires macOS 14 or later. The app is signed by JAMF Software and notarised by Apple.

Set up: create one integration in Jamf Account at the Platform environment level, then paste its client ID, secret and environment ID into Settings ▸ Jamf. The README lists the permissions it needs.

Analytics: the app sends one anonymous launch signal through TelemetryDeck. To turn it off, enable Settings ▸ Jamf ▸ Opt out of analytics.

Build 1.7.11 (5). DMG SHA-256: c144ea7221c7ea12fe33f3ce5017c0294298c16de01c533ad5f6c29e310d96b6