Notice the command comes back with different names often referred to as recipe variants
Fetch.install.recipe - To fetch and install the searched for recipe
screenFetch.munki.recipe - Specific to using Munki
Fetch.jss.recipe - you guessed it. Specific to using Jamf’s JSS
Fetch.pkg.recipe - I often use this to to extract/create/recreate an Installer package
At this stage it’s becoming obvious that we can download and recreate packages in various ways. However, it’s important to have a common place to store these packages to retrieve for later use. It’s important to have a repo for this purpose. Munki is a great option for cost and support purposes. It’s open source and has a large community supporting it. If your organization has the money to roll with JAMF then autopkg has progressively improved their support for Casper.
For Munki, it’s recommended you have macOS Server app purchased/installed. Documentation for setup is at https://github.com/munki/munki/wiki/Demonstration-Setup
Keep it simple and demonstrate creating a package:
Ok. I hear you. To receive the latest package of Firefox type the following in Terminal.
autopkg run Firefox.pkg
The following packages were built:
Identifier Version Pkg Path
---------- ------- --------
org.mozilla.firefox.pkg 49.0.2 /Users/daniel/Library/AutoPkg/Cache/com.github.autopkg.pkg.Firefox_EN/Firefox-49.0.2.pkg
The following new items were downloaded:
Using Finder I can follow the path to view the package that was built: