Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Overrides and Trust Info
Although you can run recipes themselves, it's conventional practice to create an override and include the override in your schedule. There are two reasons for this:
- The AutoPkg trust info features in AutoPkg version 1.0.0 and higher require using overrides. Running recipes or overrides without trust info will result in a recurring warning during AutoPkg runs, which will no doubt bother you.
- The purpose of a recipe override is to change certain preset variables to match your organization's needs. For example, you may want Firefox to be in a category called "Web Browsers" in your Managed Software Center app or Self Service app. An override is where you set that category.
In AutoPkgr, we've tried to simplify the process of creating and editing AutoPkg recipe overrides.
Right-click the newly-added recipe and choose Create Override. Give it a name (or leave the name as is) and click OK.
Click the checkbox next to the new override recipe, and it will be included in future scheduled AutoPkg runs.
If you wish to edit the override later, right-click the override in the recipe list and choose Open Recipe Override. The override will open using your preferred text editor.
To select which text editor to use when editing overrides, go to Folders & Integration > Configure AutoPkg > Recipe/Override Editor.
When you update recipe repos, you'll also need to update the trust information in some recipe overrides. AutoPkgr does not currently provide a way to add or update trust information, so we recommend manually using the
update-trust-info verb in AutoPkg 1.0.0+ for that purpose. You can read more about recipe trust information on the AutoPkg wiki.