### Complete Download Recipe Example

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/recipe-xml-format.md

A full example of an AutoPkg download recipe for 'defaultbrowser'. It includes input variables, processor configurations for fetching release information, and downloading the file.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Description</key>
    <string>Downloads the latest release copy of the defaultbrowser executable from kerma on Github. Set PRERELEASE to a non-empty string to download prereleases, either via Input in an override or via the -k option, i.e.: `-k PRERELEASE=yes`</string>
    
    <key>Identifier</key>
    <string>com.github.apizz.download.defaultbrowser</string>
    
    <key>Input</key>
    <dict>
        <key>NAME</key>
        <string>defaultbrowser</string>
        <key>PRERELEASE</key>
        <string></string>
    </dict>
    
    <key>MinimumVersion</key>
    <string>0.6.1</string>
    
    <key>Process</key>
    <array>
        <dict>
            <key>Arguments</key>
            <dict>
                <key>github_repo</key>
                <string>kerma/defaultbrowser</string>
                <key>include_prereleases</key>
                <string>%PRERELEASE%</string>
            </dict>
            <key>Processor</key>
            <string>GitHubReleasesInfoProvider</string>
        </dict>
        <dict>
            <key>Arguments</key>
            <dict>
                <key>filename</key>
                <string>%NAME%</string>
            </dict>
            <key>Processor</key>
            <string>URLDownloader</string>
        </dict>
        <dict>
            <key>Processor</key>
            <string>EndOfCheckPhase</string>
        </dict>
    </array>
</dict>
</plist>
```

--------------------------------

### Standard Install Recipe Structure

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/recipe-types.md

This is the standard structure for an install recipe. It inherits from a download or package recipe and uses the 'Installer' processor to install the item locally.

```xml
<dict>
    <key>Description</key>
    <string>Installs [Application] locally</string>
    <key>Identifier</key>
    <string>com.github.apizz.install.[AppName]</string>
    <key>ParentRecipe</key>
    <string>com.github.apizz.download.[AppName]</string>
    <!-- or com.github.apizz.pkg.[AppName] -->
    <key>Process</key>
    <array>
        <dict>
            <key>Arguments</key>
            <dict>
                <key>target_drive</key>
                <string>/</string>
            </dict>
            <key>Processor</key>
            <string>Installer</string>
        </dict>
    </array>
</dict>
```

--------------------------------

### Install Packages Locally with Installer

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/processors-reference.md

The Installer processor is designed for use in `.install.recipe` files to install packages locally on the system. You can specify a `target_drive` if needed, otherwise it defaults to the root volume.

```xml
<dict>
    <key>Arguments</key>
    <dict>
        <key>target_drive</key>
        <string>/</string>
    </dict>
    <key>Processor</key>
    <string>Installer</string>
</dict>
```

--------------------------------

### Munki Repository Structure Example

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/working-with-recipes.md

Illustrates a typical Munki repository directory structure for organizing packages.

```text
munki_repo/
├── pkgs/
│   ├── apps/
│   │   ├── adobeacrobat/
│   │   │   └── AdobeAcrobat2020-20.013.20066.dmg
│   │   ├── abletonlive/
│   │   │   └── AbletonLive-11.3.1.pkg
│   │   └── defaultbrowser/
│   │       └── defaultbrowser-1.2.3
│   └── ...
├── manifests/
└── catalogs/
```

--------------------------------

### Munki Import Recipe Example

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/variables-and-examples.md

This recipe downloads a package and imports it into a Munki repository, demonstrating variable substitution for repository path and package metadata.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Description</key>
    <string>Downloads Ableton Live and imports it into a Munki repository.</string>
    
    <key>Identifier</key>
    <string>com.github.apizz.munki.AbletonLive</string>
    
    <key>Input</key>
    <dict>
        <key>MUNKI_CATEGORY</key>
        <string>Music</string>
        <key>MUNKI_REPO_SUBDIR</key>
        <string>apps/abletonlive</string>
        <key>NAME</key>
        <string>AbletonLive</string>
        <key>pkginfo</key>
        <dict>
            <key>catalogs</key>
            <array>
                <string>testing</string>
            </array>
            <key>category</key>
            <string>%MUNKI_CATEGORY%</string>
            <key>description</key>
            <string>Live is fast, fluid and flexible software for music creation and performance. It comes with effects, instruments, sounds and all kinds of creative features.</string>
            <key>developer</key>
            <string>Ableton</string>
            <key>display_name</key>
            <string>Ableton Live</string>
            <key>name</key>
            <string>%NAME%</string>
            <key>unattended_install</key>
            <true/>
        </dict>
    </dict>
    
    <key>MinimumVersion</key>
    <string>1.0.0</string>
    
    <key>ParentRecipe</key>
    <string>com.github.jazzace.download.AbletonLive</string>
    
    <key>Process</key>
    <array>
        <!-- Merge version information into Munki metadata -->
        <dict>
            <key>Arguments</key>
            <dict>
                <key>additional_pkginfo</key>
                <dict>
                    <key>version</key>
                    <string>%long_version%</string>
                </dict>
            </dict>
            <key>Processor</key>
            <string>MunkiPkginfoMerger</string>
        </dict>
        
        <!-- Import package into Munki repository -->
        <dict>
            <key>Arguments</key>
            <dict>
                <key>pkg_path</key>
                <string>%pathname%</string>
                <key>repo_subdirectory</key>
                <string>%MUNKI_REPO_SUBDIR%</string>
            </dict>
            <key>Processor</key>
            <string>MunkiImporter</string>
        </dict>
    </array>
</dict>
</plist>
```

--------------------------------

### Recipe Directory Structure Example

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/recipe-xml-format.md

Organizes recipes by application name, with separate files for different recipe types.

```text
apizz-recipes/
├── AppName/
│   ├── AppName.download.recipe
│   ├── AppName.pkg.recipe
│   ├── AppName.munki.recipe
│   └── AppName.install.recipe (optional)
├── AnotherApp/
└── ...
```

--------------------------------

### Munki Package Metadata (pkginfo)

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/working-with-recipes.md

Example of metadata for a package within the Munki manifest, including name, version, display name, category, and unattended installation settings.

```xml
<dict>
    <key>name</key>
    <string>AdobeAcrobat2020</string>
    
    <key>version</key>
    <string>20.013.20066</string>
    
    <key>display_name</key>
    <string>Adobe Acrobat DC (2020 Release)</string>
    
    <key>category</key>
    <string>Applications</string>
    
    <key>developer</key>
    <string>Adobe Inc.</string>
    
    <key>description</key>
    <string>Create, review and sign PDFs. Download the official Adobe Acrobat DC application for your computer.</string>
    
    <key>catalogs</key>
    <array>
        <string>testing</string>
    </array>
    
    <key>unattended_install</key>
    <true/>
</dict>
```

--------------------------------

### Complete Munki Recipe Example for Ableton Live

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/recipe-types.md

This recipe downloads Ableton Live and imports it into a Munki repository. It specifies package information and the import process.

```xml
<dict>
    <key>Description</key>
    <string>Downloads Ableton Live and imports into Munki</string>
    <key>Identifier</key>
    <string>com.github.apizz.munki.AbletonLive</string>
    <key>Input</key>
    <dict>
        <key>MUNKI_CATEGORY</key>
        <string>Music</string>
        <key>MUNKI_REPO_SUBDIR</key>
        <string>apps/abletonlive</string>
        <key>NAME</key>
        <string>AbletonLive</string>
        <key>pkginfo</key>
        <dict>
            <key>catalogs</key>
            <array>
                <string>testing</string>
            </array>
            <key>category</key>
            <string>%MUNKI_CATEGORY%</string>
            <key>description</key>
            <string>Live is fast, fluid and flexible software for music creation and performance</string>
            <key>developer</key>
            <string>Ableton</string>
            <key>display_name</key>
            <string>Ableton Live</string>
            <key>name</key>
            <string>%NAME%</string>
            <key>unattended_install</key>
            <true/>
        </dict>
    </dict>
    <key>MinimumVersion</key>
    <string>1.0.0</string>
    <key>ParentRecipe</key>
    <string>com.github.jazzace.download.AbletonLive</string>
    <key>Process</key>
    <array>
        <dict>
            <key>Arguments</key>
            <dict>
                <key>additional_pkginfo</key>
                <dict>
                    <key>version</key>
                    <string>%long_version%</string>
                </dict>
            </dict>
            <key>Processor</key>
            <string>MunkiPkginfoMerger</string>
        </dict>
        <dict>
            <key>Arguments</key>
            <dict>
                <key>pkg_path</key>
                <string>%pathname%</string>
                <key>repo_subdirectory</key>
                <string>%MUNKI_REPO_SUBDIR%</string>
            </dict>
            <key>Processor</key>
            <string>MunkiImporter</string>
        </dict>
    </array>
</dict>
```

--------------------------------

### Real-World Example: unearth Package with ExecutableFileVersioner

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/api-reference_shared-processors.md

Illustrates how ExecutableFileVersioner is used in the unearth.pkg.recipe to extract the version from the unearth binary, then utilized in PkgCreator.

```xml
<!-- Locate the executable in the package root -->
<dict>
    <key>Arguments</key>
    <dict>
        <key>pattern</key>
        <string>%pkgroot%/usr/local/bin/unearth/unearth</string>
    </dict>
    <key>Processor</key>
    <string>FileFinder</string>
</dict>

<!-- Extract version using -v argument -->
<dict>
    <key>Arguments</key>
    <dict>
        <key>version_argument</key>
        <string>-v</string>
    </dict>
    <key>Processor</key>
    <string>com.github.apizz.apizz-recipes.SharedProcessors/ExecutableFileVersioner</string>
</dict>

<!-- Use the extracted version in package creation -->
<dict>
    <key>Arguments</key>
    <dict>
        <key>pkg_request</key>
        <dict>
            <key>version</key>
            <string>%version%</string>
        </dict>
    </dict>
    <key>Processor</key>
    <string>PkgCreator</string>
</dict>
```

--------------------------------

### Recipe File Naming Convention

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/recipe-xml-format.md

Follows the pattern {AppName}.{type}.recipe, where {type} is one of download, pkg, munki, or install.

```text
AbletonLive.munki.recipe
AdobeAcrobat2020.download.recipe
AdobeAcrobat2020.pkg.recipe
unearth.pkg.recipe
defaultbrowser.download.recipe
```

--------------------------------

### ExecutableFileVersioner: Example Output Log

Source: https://github.com/autopkg/apizz-recipes/blob/master/SharedProcessors/README.md

This log demonstrates the typical output from using FileFinder and ExecutableFileVersioner processors in an AutoPkg recipe, showing input, processing steps, and final output.

```log
FileFinder
{'Input': {'pattern': u'/Users/<user>/Library/AutoPkg/Cache/com.github.apizz.pkg.unearth/unearth/usr/local/bin/unearth/unearth'}}
FileFinder: No value supplied for find_method, setting default value of: glob
FileFinder: Found file match: '/Users/<user>/Library/AutoPkg/Cache/com.github.apizz.pkg.unearth/unearth/usr/local/bin/unearth/unearth' from globbed '/Users/ap.orlebeke/Library/AutoPkg/Cache/com.github.apizz.pkg.unearth/unearth/usr/local/bin/unearth/unearth'
{'Output': {'found_filename': u'/Users/<user>/Library/AutoPkg/Cache/com.github.apizz.pkg.unearth/unearth/usr/local/bin/unearth/unearth'}}
ExecutableFileVersioner
{'Input': {'found_filename': u'/Users/<user>/Library/AutoPkg/Cache/com.github.apizz.pkg.unearth/unearth/usr/local/bin/unearth/unearth',
           'version_argument': u'-v'}}
ExecutableFileVersioner: No value supplied for interpreter_path, setting default value of: /usr/bin/python
ExecutableFileVersioner: Found executable at /Users/<user>/Library/AutoPkg/Cache/com.github.apizz.pkg.unearth/unearth/usr/local/bin/unearth/unearth
ExecutableFileVersioner: Version: 0.0.1
{'Output': {'version': '0.0.1'}}
```

--------------------------------

### Recipe Description Key Example

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/recipe-xml-format.md

The Description key provides a human-readable explanation of the recipe's purpose. It should be concise and mention any special requirements or input variables.

```xml
<key>Description</key>
<string>Downloads the latest version of Ableton Live and imports it into a munki_repo.

Make an override of this recipe in order to specify the necessary Ableton Live download information, including LIVE_VERS and EDITION</string>
```

--------------------------------

### Recipe MinimumVersion Key Example

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/recipe-xml-format.md

The MinimumVersion key specifies the minimum required AutoPkg version for the recipe. Common values range from 0.4.0 to 1.0.0.

```xml
<key>MinimumVersion</key>
<string>1.0.0</string>
```

--------------------------------

### Run Munki Recipes Daily with AutoPkg

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/README.md

Example command to run multiple Munki recipes daily using AutoPkg. This is typically used in cron jobs or LaunchAgents.

```bash
# Example: Run all Munki recipes daily
# In cron or LaunchAgent:
/usr/local/bin/autopkg run \
  com.github.apizz.munki.AbletonLive \
  com.github.apizz.munki.defaultbrowser \
  com.github.apizz.munki.unearth \
  ... (more recipes)
```

--------------------------------

### Add apizz-recipes Repo to AutoPkg

Source: https://github.com/autopkg/apizz-recipes/blob/master/LoggerPro_License/README.md

Add the apizz-recipes repository to your AutoPkg setup to access the provided recipes.

```bash
autopkg repo-add https://github.com/autopkg/apizz-recipes.git
```

--------------------------------

### Munki Catalog Assignment Example

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/working-with-recipes.md

Specifies the Munki catalogs a package will be added to, controlling its visibility and deployment.

```xml
<key>catalogs</key>
<array>
    <string>testing</string>
    <!-- Package appears in "testing" catalog for limited rollout -->
</array>
```

--------------------------------

### PkgCreator: Basic Package Request

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/processors-reference.md

This example shows a typical `pkg_request` for the PkgCreator processor. It includes essential package information like ID, name, version, and file ownership settings.

```xml
<dict>
    <key>Arguments</key>
    <dict>
        <key>pkg_request</key>
        <dict>
            <key>id</key>
            <string>com.github.unearth</string>
            <key>pkgname</key>
            <string>unearth</string>
            <key>version</key>
            <string>%version%</string>
            <key>chown</key>
            <array>
                <dict>
                    <key>path</key>
                    <string>usr</string>
                    <key>user</key>
                    <string>root</string>
                    <key>group</key>
                    <string>wheel</string>
                    <key>mode</key>
                    <string>0755</string>
                </dict>
            </array>
        </dict>
    </dict>
    <key>Processor</key>
    <string>PkgCreator</string>
</dict>
```

--------------------------------

### Recipe Process Key Example

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/recipe-xml-format.md

The Process key is a required array of processor dictionaries that define the recipe's execution steps. Processors execute sequentially, with output from one feeding into the next.

```xml
<key>Process</key>
<array>
    <dict>
        <!-- Processor 1 -->
    </dict>
    <dict>
        <!-- Processor 2 -->
    </dict>
</array>
```

--------------------------------

### Recipe Input Key Example

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/recipe-xml-format.md

The Input key is an optional dictionary defining variables that can be overridden at recipe invocation time. Each variable has a key name and a default value.

```xml
<key>Input</key>
<dict>
    <key>NAME</key>
    <string>AbletonLive</string>
    
    <key>MUNKI_CATEGORY</key>
    <string>Music</string>
    
    <key>MUNKI_REPO_SUBDIR</key>
    <string>apps/abletonlive</string>
    
    <key>PRERELEASE</key>
    <string></string>
    <!-- Empty string = default value -->
    
    <key>pkginfo</key>
    <dict>
        <!-- Nested configuration dictionary -->
    </dict>
</dict>
```

--------------------------------

### ExecutableFileVersioner: Shell Script Example

Source: https://github.com/autopkg/apizz-recipes/blob/master/SharedProcessors/README.md

Use this snippet for a shell script where the version argument is `version`. It specifies the interpreter path as `/bin/sh` and requires FileFinder to locate the script.

```plist
<dict>
    <key>Arguments</key>
    <dict>
        <key>pattern</key>
        <string>%RECIPE_CACHE_DIR%/path/to/executable.sh</string>
    </dict>
    <key>Processor</key>
    <string>FileFinder</string>
</dict>
<dict>
    <key>Arguments</key>
    <dict>
        <key>interpreter_path</key>
        <string>/bin/sh</string>
        <key>version_argument</key>
        <string>version</string>
    </dict>
    <key>Processor</key>
    <string>ExecutableFileVersioner</string>
</dict>
```

--------------------------------

### Basic Recipe Execution with Autopkg

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/README.md

Demonstrates fundamental autopkg commands for finding recipes, running download and Munki import recipes, and overriding variables at runtime.

```bash
# Find a recipe
ls -la apizz-recipes/defaultbrowser/
```

```bash
# Run the download recipe
autopkg run com.github.apizz.download.defaultbrowser
```

```bash
# Run the Munki import recipe (includes parent download steps)
autopkg run com.github.apizz.munki.defaultbrowser
```

```bash
# Override variables at runtime
autopkg run com.github.apizz.munki.defaultbrowser \
    -k MUNKI_CATEGORY="System Tools"
```

--------------------------------

### Check PKG Installer Signature

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/working-with-recipes.md

Use pkgutil to check the signature of a PKG installer file. This is useful for verifying the integrity of software packages.

```bash
# Check a PKG
pkgutil --check-signature /path/to/installer.pkg
```

--------------------------------

### Run a Download Recipe

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/working-with-recipes.md

Execute a download recipe using the `autopkg run` command followed by the recipe's identifier. This initiates the download process for the specified software.

```bash
autopkg run com.github.apizz.download.defaultbrowser
```

--------------------------------

### Verify Downloaded File Signature

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/README.md

Verify the code signature of a downloaded file to ensure its integrity and authenticity before installation. Supports both disk image (.dmg) and installer package (.pkg) files.

```bash
codesign -v /path/to/file.dmg
```

```bash
codesign -v /path/to/installer.pkg
```

--------------------------------

### Array of Strings Example: Munki Catalogs

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/recipe-xml-format.md

Specifies an array of strings for Munki catalog names.

```xml
<!-- Munki catalogs (array of strings) -->
<key>catalogs</key>
<array>
    <string>testing</string>
    <string>production</string>
</array>
```

--------------------------------

### Array of Dictionaries Example: File Ownership

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/recipe-xml-format.md

Defines an array of dictionaries to specify file ownership and permissions.

```xml
<!-- File ownership specifications (array of dicts) -->
<key>chown</key>
<array>
    <dict>
        <key>path</key>
        <string>usr</string>
        <key>user</key>
        <string>root</string>
        <key>group</key>
        <string>wheel</string>
        <key>mode</key>
        <string>0755</string>
    </dict>
</array>
```

--------------------------------

### Array of Strings Example: Certificate Authorities

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/recipe-xml-format.md

Defines an array of strings for expected certificate authority names.

```xml
<!-- Certificate authority chain (array of strings) -->
<key>expected_authority_names</key>
<array>
    <string>Developer ID Installer: Adobe Inc. (JQ525L2MZD)</string>
    <string>Developer ID Certification Authority</string>
    <string>Apple Root CA</string>
</array>
```

--------------------------------

### Path Construction with Variables

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/variables-and-examples.md

Shows how to construct file paths by combining predefined variables like %RECIPE_CACHE_DIR% and %NAME%.

```xml
<!-- %RECIPE_CACHE_DIR% = "/Users/user/Library/AutoPkg/Cache/com.github.apizz.pkg.unearth" -->
<!-- %NAME% = "unearth" -->

<key>pkgroot</key>
<string>%RECIPE_CACHE_DIR%/%NAME%</string>
<!-- Result: "/Users/user/Library/AutoPkg/Cache/com.github.apizz.pkg.unearth/unearth" -->
```

--------------------------------

### Enable Pre-release Downloads in Recipes

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/working-with-recipes.md

Configure recipes to download pre-release versions by setting the PRERELEASE input key. An empty value defaults to stable releases.

```xml
<key>Input</key>
<dict>
    <key>PRERELEASE</key>
    <string></string>
    <!-- Empty = stable only; set to any non-empty value for pre-releases -->
</dict>
```

--------------------------------

### Case Sensitivity of Variables

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/recipe-xml-format.md

Illustrates that variable names in AutoPkg recipes are case-sensitive, providing examples of different casing for the same variable.

```xml
<!-- These are different: -->
<string>%NAME%</string>
<string>%name%</string>
<string>%Name%</string>
```

--------------------------------

### Pattern: Reference processor output

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/variables-and-examples.md

Demonstrates how to pass output from one processor (e.g., `URLDownloader` setting `%pathname%`) as an argument to a subsequent processor (e.g., `Unarchiver`). This enables data flow between recipe steps.

```xml
<!-- Step 1: URLDownloader sets %pathname% -->
<dict>
    <key>Processor</key>
    <string>URLDownloader</string>
</dict>

<!-- Step 2: Reference %pathname% in next processor -->
<dict>
    <key>Arguments</key>
    <dict>
        <key>archive_path</key>
        <string>%pathname%</string>
    </dict>
    <key>Processor</key>
    <string>Unarchiver</string>
</dict>
```

--------------------------------

### Munki Configuration in Recipes Input

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/working-with-recipes.md

Shows how to define Munki-related inputs within a recipe, including package name, category, repository subdirectory, and pkginfo details.

```xml
<key>Input</key>
<dict>
    <key>NAME</key>
    <string>AdobeAcrobat2020</string>
    
    <key>MUNKI_CATEGORY</key>
    <string>Applications</string>
    
    <key>MUNKI_REPO_SUBDIR</key>
    <string>apps/adobeacrobat</string>
    
    <key>pkginfo</key>
    <dict>
        <key>category</key>
        <string>%MUNKI_CATEGORY%</string>
        
        <key>display_name</key>
        <string>Adobe Acrobat DC (2020 Release)</string>
        
        <key>developer</key>
        <string>Adobe Inc.</string>
        
        <key>description</key>
        <string>Create, review and sign PDFs...</string>
        
        <key>catalogs</key>
        <array>
            <string>testing</string>
        </array>
        
        <key>unattended_install</key>
        <true/>
    </dict>
</dict>
```

--------------------------------

### Create a Package for Deployment

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/README.md

This command builds a deployable PKG from a downloaded binary. AutoPkg will execute the parent download recipe, restructure files, extract version information, and create the PKG.

```bash
# Build a PKG from the downloaded binary
autopkg run com.github.apizz.pkg.unearth -v

# AutoPkg will:
# 1. Run parent download recipe
# 2. Extract/restructure files
# 3. Extract version information
# 4. Create deployment-ready PKG
```

--------------------------------

### Recipe Identifier Key Example

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/recipe-xml-format.md

The Identifier key is a required, unique, reverse-domain-notation string for the recipe. It follows the format com.github.apizz.{type}.{AppName}.

```xml
<key>Identifier</key>
<string>com.github.apizz.download.AdobeAcrobat2020</string>
```

--------------------------------

### Run a Munki Import Recipe

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/working-with-recipes.md

Execute a Munki import recipe. This command automatically includes and runs the necessary parent download steps before importing into Munki.

```bash
autopkg run com.github.apizz.munki.AbletonLive
```

--------------------------------

### GitHubReleasesInfoProvider for GitHub Downloads

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/recipe-types.md

Uses GitHubReleasesInfoProvider to fetch release information from a GitHub repository. This processor is typically followed by URLDownloader to get the actual asset.

```xml
<dict>
    <key>Arguments</key>
    <dict>
        <key>github_repo</key>
        <string>kerma/defaultbrowser</string>
        <key>include_prereleases</key>
        <string>%PRERELEASE%</string>
    </dict>
    <key>Processor</key>
    <string>GitHubReleasesInfoProvider</string>
</dict>
```

--------------------------------

### Modify Input Variables in Override File

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/working-with-recipes.md

Edit the generated override file to change input variables. This example shows how to modify the MUNKI_REPO_SUBDIR and MUNKI_CATEGORY for a recipe.

```xml
<key>Input</key>
<dict>
    <key>NAME</key>
    <string>defaultbrowser</string>
    <key>MUNKI_REPO_SUBDIR</key>
    <string>apps/defaultbrowser</string>
    <key>MUNKI_CATEGORY</key>
    <string>Applications</string>
</dict>
```

```xml
<key>Input</key>
<dict>
    <key>NAME</key>
    <string>defaultbrowser</string>
    <key>MUNKI_REPO_SUBDIR</key>
    <string>apps/system-tools</string>
    <key>MUNKI_CATEGORY</key>
    <string>System Utilities</string>
</dict>
```

--------------------------------

### Recipe ParentRecipe Key Example

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/recipe-xml-format.md

The ParentRecipe key is an optional string identifier for a parent recipe to inherit from. This allows for extending functionality and sharing input variables.

```xml
<key>ParentRecipe</key>
<string>com.github.apizz.download.AdobeAcrobat2020</string>
```

--------------------------------

### List Recipes in a Directory

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/working-with-recipes.md

Use the `ls` command to view all recipe files within a specific application directory. This is helpful for exploring the available recipes for a particular software.

```bash
ls -la ./defaultbrowser/
```

--------------------------------

### Testing ExecutableFileVersioner Manually

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/api-reference_shared-processors.md

Demonstrates how to manually test the ExecutableFileVersioner by first finding an executable and then showing the command the processor would execute.

```bash
# Find the unearth executable
/path/to/unearth -v

# The ExecutableFileVersioner will execute:
/usr/bin/python /path/to/unearth -v

# Output (example):
# Version: 0.0.1
```

--------------------------------

### Extract Executable Version Argument

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/recipe-patterns.md

Use ExecutableFileVersioner to get the version from an executable by passing a version argument. This works for any command-line tool that supports a version flag.

```xml
<dict>
    <key>Arguments</key>
    <dict>
        <key>pattern</key>
        <string>%pkgroot%/usr/local/bin/app</string>
    </dict>
    <key>Processor</key>
    <string>FileFinder</string>
</dict>
<dict>
    <key>Arguments</key>
    <dict>
        <key>version_argument</key>
        <string>--version</string>
    </dict>
    <key>Processor</key>
    <string>com.github.apizz.apizz-recipes.SharedProcessors.ExecutableFileVersioner</string>
</dict>
```

--------------------------------

### Get GitHub Release Version

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/recipe-patterns.md

Employ GitHubReleasesInfoProvider to automatically extract version information from GitHub release tags. This method is convenient as it requires no additional processing.

```xml
<dict>
    <key>Arguments</key>
    <dict>
        <key>github_repo</key>
        <string>owner/repo</string>
    </dict>
    <key>Processor</key>
    <string>GitHubReleasesInfoProvider</string>
</dict>
```

--------------------------------

### Enable Pre-releases at Runtime

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/working-with-recipes.md

Override the PRERELEASE setting at runtime using the '-k' flag with the 'autopkg run' command.

```bash
autopkg run com.github.apizz.download.defaultbrowser -k PRERELEASE=yes
```

--------------------------------

### CodeSignatureVerifier Certificate Authority Chain Example

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/processors-reference.md

Specifies the expected certificate authority chain for verifying a code signature. Include the full chain from the leaf certificate to the root.

```xml
<key>expected_authority_names</key>
<array>
    <string>Developer ID Installer: Adobe Inc. (JQ525L2MZD)</string>
    <string>Developer ID Certification Authority</string>
    <string>Apple Root CA</string>
</array>
```

--------------------------------

### ExecutableFileVersioner Usage Pattern

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/api-reference_shared-processors.md

Demonstrates the typical sequence of using FileFinder to locate an executable, followed by ExecutableFileVersioner to extract its version, and finally PkgCreator to use the extracted version.

```xml
<!-- Step 1: Locate the executable -->
<dict>
    <key>Arguments</key>
    <dict>
        <key>pattern</key>
        <string>%RECIPE_CACHE_DIR%/path/to/executable</string>
    </dict>
    <key>Processor</key>
    <string>FileFinder</string>
</dict>

<!-- Step 2: Extract version from the executable -->
<dict>
    <key>Arguments</key>
    <dict>
        <key>version_argument</key>
        <string>--version</string>
    </dict>
    <key>Processor</key>
    <string>com.github.apizz.apizz-recipes.SharedProcessors/ExecutableFileVersioner</string>
</dict>

<!-- Step 3: Use extracted version in subsequent steps -->
<dict>
    <key>Arguments</key>
    <dict>
        <key>version</key>
        <string>%version%</string>
    </dict>
    <key>Processor</key>
    <string>PkgCreator</string>
</dict>
```

--------------------------------

### Simple GitHub Download Recipe

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/variables-and-examples.md

This recipe downloads the latest release of a GitHub project. Set the PRERELEASE variable to a non-empty string to download pre-releases.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Description</key>
    <string>Downloads the latest release of defaultbrowser from GitHub. Set PRERELEASE to a non-empty string to download pre-releases.</string>
    
    <key>Identifier</key>
    <string>com.github.apizz.download.defaultbrowser</string>
    
    <key>Input</key>
    <dict>
        <key>NAME</key>
        <string>defaultbrowser</string>
        <key>PRERELEASE</key>
        <string></string>
    </dict>
    
    <key>MinimumVersion</key>
    <string>0.6.1</string>
    
    <key>Process</key>
    <array>
        <!-- Query GitHub API for latest release -->
        <dict>
            <key>Arguments</key>
            <dict>
                <key>github_repo</key>
                <string>kerma/defaultbrowser</string>
                <key>include_prereleases</key>
                <string>%PRERELEASE%</string>
            </dict>
            <key>Processor</key>
            <string>GitHubReleasesInfoProvider</string>
        </dict>
        
        <!-- Download the binary using URL from above -->
        <dict>
            <key>Arguments</key>
            <dict>
                <key>filename</key>
                <string>%NAME%</string>
            </dict>
            <key>Processor</key>
            <string>URLDownloader</string>
        </dict>
        
        <!-- Mark end of check phase -->
        <dict>
            <key>Processor</key>
            <string>EndOfCheckPhase</string>
        </dict>
    </array>
</dict>
</plist>
```

--------------------------------

### Autopkg Recipe Chain Pattern

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/README.md

Visualizes the common sequence of recipe types: download, package (optional), and Munki import, showing the flow of artifacts.

```text
download.recipe
    │
    ├─ PKG ingredients from vendor
    │
pkg.recipe (optional)
    │
    ├─ Repackaged PKG for deployment
    │
munki.recipe
    │
    └─ Imported to Munki with metadata
```

--------------------------------

### Standard Munki Import Recipe Pattern

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/overview.md

This pattern illustrates a standard recipe for importing packages into a Munki repository. It shows how to merge additional metadata before the final import step.

```xml
<ParentRecipe>com.github.apizz.download.[AppName]</ParentRecipe>
<Process>
  <dict>
    <key>Processor</key>
    <string>MunkiPkginfoMerger</string>
    <!-- Merge additional metadata -->
  </dict>
  <dict>
    <key>Processor</key>
    <string>MunkiImporter</string>
  </dict>
</Process>
```

--------------------------------

### ExecutableFileVersioner: Python Script Example

Source: https://github.com/autopkg/apizz-recipes/blob/master/SharedProcessors/README.md

Use this snippet when processing a Python script where the version argument is `--version`. It requires the FileFinder processor to locate the executable first.

```plist
<dict>
    <key>Arguments</key>
    <dict>
        <key>pattern</key>
        <string>%RECIPE_CACHE_DIR%/path/to/executable.py</string>
    </dict>
    <key>Processor</key>
    <string>FileFinder</string>
</dict>
<dict>
    <key>Arguments</key>
    <dict>
        <key>version_argument</key>
        <string>--version</string>
    </dict>
    <key>Processor</key>
    <string>ExecutableFileVersioner</string>
</dict>
```

--------------------------------

### Standard Download Recipe Pattern

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/overview.md

This pattern demonstrates a typical sequence for downloading a file using AutoPkg. It includes processors for fetching release information or direct URLs, verifying code signatures, and marking the end of the check phase.

```xml
<Process>
  <dict>
    <key>Processor</key>
    <string>GitHubReleasesInfoProvider</string>
    <!-- or URLDownloader for direct URLs -->
  </dict>
  <dict>
    <key>Processor</key>
    <string>CodeSignatureVerifier</string>
  </dict>
  <dict>
    <key>Processor</key>
    <string>EndOfCheckPhase</string>
  </dict>
</Process>
```

--------------------------------

### LoggerPro3.pkg.recipe: PkgCopier and PathDeleter Processors

Source: https://github.com/autopkg/apizz-recipes/blob/master/LoggerPro_License/README.md

The PkgCopier processor renames the original installer package to the standard AutoPkg format (%NAME%-%version%.pkg). The PathDeleter then cleans up the temporary unpacked directories.

```plist
<dict>
    <key>Arguments</key>
    <dict>
	<key>pkg_path</key>
	<string>%RECIPE_CACHE_DIR%/%NAME%-%version%.pkg</string>
	<key>source_pkg</key>
	<string>%pathname%/Install Logger Pro %MAJOR_VERSION%.pkg</string>
    </dict>
    <key>Processor</key>
    <string>PkgCopier</string>
</dict>
<dict>
    <key>Arguments</key>
    <dict>
	<key>path_list</key>
	<array>
	    <string>%RECIPE_CACHE_DIR%/unpack</string>
	</array>
    </dict>
    <key>Processor</key>
    <string>PathDeleter</string>
</dict>
```

--------------------------------

### Complex Package Building Recipe (XML)

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/variables-and-examples.md

This XML recipe defines the process for building a macOS PKG. It includes steps for creating directory structures, extracting archives, copying files, and generating the final package. Ensure the 'ParentRecipe' is downloaded before this recipe runs.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Description</key>
    <string>Builds a macOS PKG from the unearth binary archive.</string>
    
    <key>Identifier</key>
    <string>com.github.apizz.pkg.unearth</string>
    
    <key>Input</key>
    <dict>
        <key>NAME</key>
        <string>unearth</string>
    </dict>
    
    <key>MinimumVersion</key>
    <string>0.6.1</string>
    
    <key>ParentRecipe</key>
    <string>com.github.apizz.download.unearth</string>
    
    <key>Process</key>
    <array>
        <!-- Step 1: Create directory structure for package -->
        <dict>
            <key>Arguments</key>
            <dict>
                <key>pkgroot</key>
                <string>%RECIPE_CACHE_DIR%/%NAME%</string>
                <key>pkgdirs</key>
                <dict>
                    <key>usr</key>
                    <string>0755</string>
                    <key>usr/local/</key>
                    <string>0755</string>
                    <key>usr/local/bin/</key>
                    <string>0775</string>
                    <key>usr/local/bin/unearth/</key>
                    <string>0775</string>
                </dict>
            </dict>
            <key>Processor</key>
            <string>PkgRootCreator</string>
        </dict>
        
        <!-- Step 2: Extract downloaded archive -->
        <dict>
            <key>Arguments</key>
            <dict>
                <key>archive_path</key>
                <string>%pathname%</string>
                <key>destination_path</key>
                <string>%RECIPE_CACHE_DIR%/unpack</string>
                <key>purge_destination</key>
                <true/>
            </dict>
            <key>Processor</key>
            <string>Unarchiver</string>
        </dict>
        
        <!-- Step 3: Copy main executable -->
        <dict>
            <key>Arguments</key>
            <dict>
                <key>source_path</key>
                <string>%RECIPE_CACHE_DIR%/unpack/unearth-master/unearth</string>
                <key>destination_path</key>
                <string>%pkgroot%/usr/local/bin/unearth/</string>
                <key>overwrite</key>
                <false/>
            </dict>
            <key>Processor</key>
            <string>Copier</string>
        </dict>
        
        <!-- Step 4: Copy supporting files -->
        <dict>
            <key>Arguments</key>
            <dict>
                <key>source_path</key>
                <string>%RECIPE_CACHE_DIR%/unpack/unearth-master/artifacts/</string>
                <key>destination_path</key>
                <string>%pkgroot%/usr/local/bin/unearth/artifacts</string>
                <key>overwrite</key>
                <true/>
            </dict>
            <key>Processor</key>
            <string>Copier</string>
        </dict>
        
        <!-- Step 5: Find the executable for version extraction -->
        <dict>
            <key>Arguments</key>
            <dict>
                <key>pattern</key>
                <string>%pkgroot%/usr/local/bin/unearth/unearth</string>
            </dict>
            <key>Processor</key>
            <string>FileFinder</string>
        </dict>
        
        <!-- Step 6: Extract version from executable -->
        <dict>
            <key>Arguments</key>
            <dict>
                <key>version_argument</key>
                <string>-v</string>
            </dict>
            <key>Processor</key>
            <string>com.github.apizz.apizz-recipes.SharedProcessors/ExecutableFileVersioner</string>
        </dict>
        
        <!-- Step 7: Create the final PKG -->
        <dict>
            <key>Arguments</key>
            <dict>
                <key>pkg_request</key>
                <dict>
                    <key>chown</key>
                    <array>
                        <dict>
                            <key>group</key>
                            <string>wheel</string>
                            <key>mode</key>
                            <string>0755</string>
                            <key>path</key>
                            <string>usr</string>
                            <key>user</key>
                            <string>root</string>
                        </dict>
                    </array>
                    <key>id</key>
                    <string>com.github.unearth</string>
                    <key>pkgname</key>
                    <string>%NAME%</string>
                    <key>version</key>
                    <string>%version%</string>
                </dict>
            </dict>
            <key>Processor</key>
            <string>PkgCreator</string>
        </dict>
    </array>
</dict>
</plist>
```

--------------------------------

### Providing Default Input Variables in XML

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/recipe-patterns.md

Demonstrates how to define default values for input variables within the <key>Input</key> dictionary in an AutoPkg recipe's XML configuration. This ensures variables have a sensible default if not explicitly overridden.

```xml
<key>Input</key>
<dict>
    <key>NAME</key>
    <string>AbletonLive</string>
    <!-- Default value if not overridden -->
    
    <key>PRERELEASE</key>
    <string></string>
    <!-- Empty string = disabled by default -->
</dict>
```

--------------------------------

### PkgCreator: Define File Ownership

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/processors-reference.md

Use the `chown` array within the `pkg_request` to specify ownership and permissions for files and directories within the package. This is useful for ensuring correct file system integrity after installation.

```xml
<key>chown</key>
<array>
    <dict>
        <key>path</key>
        <string>usr</string>
        <key>user</key>
        <string>root</string>
        <key>group</key>
        <string>wheel</string>
        <key>mode</key>
        <string>0755</string>
    </dict>
</array>
```

--------------------------------

### Search for a Recipe (Dry-Run)

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/working-with-recipes.md

Use `autopkg search` to check if a recipe is available and valid without executing its download or import steps. This is a safe way to verify recipe existence.

```bash
autopkg search com.github.apizz.download.defaultbrowser
```

--------------------------------

### Get Detailed Certificate Information

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/working-with-recipes.md

Retrieve detailed information about an application's code signature, specifically focusing on the authority names. The 'grep "Authority"' command filters the output to show only the relevant lines.

```bash
# Get certificate details
codesign -dvv /Applications/SomeApp.app | grep "Authority"
```

--------------------------------

### Repository Structure Overview

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/README.md

Illustrates the typical directory layout for apizz-recipes, showing application-specific recipe folders and shared processors.

```tree
apizz-recipes/
├── Adobe_Acrobat/
│   ├── AdobeAcrobat2020.download.recipe    (Download from vendor)
│   ├── AdobeAcrobat2020.pkg.recipe         (Repackage to PKG)
│   └── AdobeAcrobat2020.munki.recipe       (Import to Munki)
├── SharedProcessors/
│   ├── ExecutableFileVersioner.py          (Custom processor)
│   ├── SharedProcessors.recipe             (Registration)
│   └── README.md
└── [100+ more applications]
```

--------------------------------

### Custom Certificate Requirement String

Source: https://github.com/autopkg/apizz-recipes/blob/master/_autodocs/working-with-recipes.md

This XML snippet defines a custom requirement string for precise certificate matching. It includes specific OIDs and fields to ensure the certificate meets stringent criteria, such as identifying Developer ID Installer certificates.

```xml
<key>requirement</key>
<string>anchor apple generic and (certificate leaf[field.1.2.840.113635.100.6.1.9] /* exists */ or certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = JQ525L2MZD)</string>
```