Assets 3

Introduction

This is the official release of Munki 3.0, a major update to the Munki tools.
This is the same build as Beta 10 and Release Candidate 1.

Read more about Munki 3 here: https://github.com/munki/munki/wiki/Munki-3-Information

Munki 3 is considered stable and suitable for production use, but you may want to roll it out in stages.

New features/changes information:

  • "Native" support for macOS installation applications (Like "Install macOS Sierra.app").

  • Support for authorized restarts.
    This requires some launchd changes that will require a restart when upgrading from Munki 2.x to 3.x.

  • Notification Manager notification support.
    This requires some launchd changes that will require a restart when upgrading from Munki 2.x to 3.x.

  • Repo plugin support contributed by Centrify.
    Allows the creation of plugins to enable the Munki command-line tools to work with cloud-based repos, or repos not available via traditional file paths, or to add additional capabilities/actions when working with a file-based repo.
    There are a couple of sample/demonstration plugins included: a GitFileRepo plugin for better integration with Git repos, and a MWA2APIPlugin as an example of working with a repo that doesn't have direct filesystem access.

  • Auto-removal of optionally-installed applications that have not been used in an admin-specified time period.

  • Support for a new "Featured" psuedo-category to be used with Managed Software Center. Items can be added to a list of "featured_items" in a manifest. If there are optional installs that are also in the list of "featured_items", the display of All optional installs in MSC app will be replaced by a display of Featured items.

  • Support for allowing the install of packages signed with untrusted or expired certificates.

  • Change in behavior for 'application' items in lists of installs: if such an item includes a value for 'path', only that path will be compared against. If 'path' does not exist and CFBundleName or CFBundleIdentifier do exist, Munki will consider locally-installed applications that have matching CFBundleName or CFBundleIdentifier for comparision.

See https://github.com/munki/munki/wiki/Munki-3-Information#munki-3-new-features for more information on the new features.