Overrides and Trust Info

Elliot Jordan edited this page Dec 23, 2016 · 1 revision

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.

  1. Right-click the newly-added recipe and choose Create Override. Give it a name (or leave the name as is) and click OK.

  2. 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.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.