Munki 2.2 Official Release
This is the official release of Munki 2.2.
Munki 2.2 adds "native" support for configuration profiles. Instead of having to wrap a configuration profile in a package to be able to deploy with Munki, Munki now supports configuration profiles as an item it knows how to install and remove without "wrapping".
Use munkiimport /path/to/some.mobileconfig
to import a .mobileconfig file into your Munki repo. From there, you can treat it in manifests as you would any other piece of software -- you can add it to managed_installs, managed_uninstalls, optional_installs, etc.
Additionally, Munki 2.2 introduces new functionality that should dramatically reduce the number of http/https requests to your Munki web server. pkginfo items may now contain an icon_hash, which is a sha256 hash of the expected icon file. If the icon file currently cached on the local machine has the same sha256 hash, no http/https request will be made for the icon for the item.
Changes since 2.1.1:
- Added support for configuration profiles as a "native" item Munki knows how to install and remove.
- Remove '-f' flag from
make_munki_mpkg_from_git.sh
's usage message. Thanks to Richard Lafontaine. - make_munki_mpkg_from_git.sh has been updated to no longer complain if PackageMaker (!) is not installed.
- New support for an icon_hash key in pkginfo: if this key contains a sha256 hash value matching the sha256 hash of a previously downloaded icon file, managedsoftwareupdate will not request the icon from the Munki webserver. This will reduce HTTP(S) requests to your Munki server(s) during a managedsoftwareupdate run. Contributed by eigerman@google.com.
- munkiimport now generates an icon_hash in the pkginfo if an icon for the item being imported is present (or is also being imported). Thanks to Arjen van Bochoven.
- makecatalogs now dynamically generates icon_hash keys and values for pkginfo items that point to available icons. Thanks to Sam Keeley.