Home
JumpCloud can leverage AutoPkg to automate package testing and deployment through the JumpCloud AutoPkg Importer. Those familiar with AutoPkg can develop their own .pkg overrides which invoke the JumpCloud AutoPkg Importer processor. To learn more about AutoPkg, visit the AutoPkg wiki page for documentation. The JumpCloud AutoPkg Importer was designed to process AutoPkg .pkg recipes, upload packages to distribution points and dynamically create JumpCloud commands and groups.
The JumpCloud AutoPkg Importer is an AutoPkg recipe processor designed to help automate software deployments and updates.
This processor is in early access, functionality may change over time. The JC-AutoPkg-Importer uses Amazon Web Services S3 Buckets to store .pkg files and the JumpCloud APIs to generate dynamic commands which link to the objects stored in S3.
In general, the intended use of this processor is to enable the following workflow:
Software .pkg files are generated from AutoPkg .pkg Recipes. That software package is uploaded to an AWS S3 Bucket for storage. A link to that bucket object is then generated. A dynamic group and command are generated in JumpCloud. The dynamic JumpCloud system group contains systems that don't have or require the updated version of that software package. The dynamic JumpCloud command targets the system group and installs the software package uploaded to the AWS S3 Bucket. The command is run and JumpCloud systems install the latest version of the software package.
The workflow should be throughly tested before deploying to development systems. Additional deployment scenarios are outlined in the software deployment wiki page.
Although the JumpCloud-AutoPkg-Importer is licensed under Apache the various libraries required to run the processor may be licensed under a different software license agreement. By using the JumpCloud API python library in this project you agree to the JumpCloud Terms and Service.