Blockblock autopkg recipe install#
Blockblock autopkg recipe Patch#
Blockblock autopkg recipe full#
Blockblock autopkg recipe pro#

Please note that I don’t use these recipes, as my organisation’s requirements are not the same as that “standard” design. These are now in the grahampugh-recipes repo (see the Jamf_Recipes and Jamf_Package_Upload_Only folders), and they are searchable via the autopkg search command. Since it’s possible to run this against a recipe list, I decided to convert all the working recipes in the jss-recipes repo to. One more thing! I’ve already used JamfRecipeMaker to make around 100. But let me know if you encounter any problems with that.

Blockblock autopkg recipe install#

The processor will attempt to install ruamel.yaml into the AutoPkg python library if missing, so you shouldn’t have to do anything in advance to make this work. That’s because I yanked most of the code from my existing plist-yaml-plist project for converting PLIST to YAML and vice versa. There are some additional requirements, specifically the ruamel.yaml python module. No, so long as you have added the grahampugh-recipes repo, you should be good to go. Do I have to install anything special to use JamfRecipeMaker?

Blockblock autopkg recipe full#

pkg recipe.ĭefaults write ~/Library/Preferences/ RECIPE_OUTPUT_PATH /path/to/my/recipe-repo/Jamf_Recipesįor full documentation, incluiding more options for feeding in variables, see the JamfRecipeMaker wiki. jss recipe (we only need ParentRecipe and NAME), so can be run directly from a. jamf recipe do not need any information from a. jss-upload recipes as was described in Daz Wallace’s 2019 blog post Using Autopkg for package Uploads to Jamf Cloud only. (1) Create a recipe that just uploads a package and nothing else. We can use JamfRecipeMaker as a pre-processor (or post-processor if you like) when running a. This is pretty much what Elliot Jordan’s excellent Recipe Robot app is doing when generating a. We just need to write these to a file in the correct structure of a. jss recipe, the only values we really need to obtain are: Sounds weird, but when you run an AutoPkg recipe, all the relevant variable values are written as environment variables, so it’s all available for doing whatever you want. Huh? An AutoPkg processor that reads one recipe and writes another?Įxactly. jss recipe while running it, and writes a new. To help achieve this, I’ve developed a novel idea - a new AutoPkg processor that reads from a. jss recipes that are currently available in the jss-recipes and various other repos, notably rtrouton-recipes. jamf recipe that do exactly the same thing as those existing “standard”. jss recipes, you may be contemplating having to write a bunch of. However, if your policy and smart group design is compatible with the “standard” design devised for.

Blockblock autopkg recipe Patch#

For example, if you’re using Patch Management, or creating multiple policies, JSSImporter recipes were not well designed for this, and you can benefit from the new opportunities available with JamfUploader. JamfUploader is designed to be more flexible than JSSImporter, so a straight conversion may well not be the best course of action. jss) recipes, so new recipes need to be written. The design is significantly different to JSSImporter-based (. jamf) recipes are modular in design (see my original blog post, JamfUploader - new AutoPkg processors for importing packages to Jamf Pro).

Blockblock autopkg recipe pro#

The JamfUploader project is my replacement of JSSImporter, for Jamf Pro customers that want to continue to benefit from the power of AutoPkg for obtaining deployable packages for thousands of third party applications and other software. In case you missed it, the JSSImporter processor is deprecated, and will cease to function when Jamf remove basic authentication from the Classic API endpoints, which they have announced will happen sometime between August and December 2022.