Skip to content
Joe Workman edited this page Aug 28, 2020 · 11 revisions

JumpCloud AutoPkg Importer

automate it and relax

JumpCloud can leverage AutoPkg to automate software testing and deployment through JumpCloud commands. 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.

At a glance

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.

autopkg workflow

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.

Note on licensing

Although the JumpCloud-AutoPkg-Importer is licensed under the Apache 2.0 license, the various libraries required to run the processor may be licensed under different terms. Please check the applicable terms for each library or component. By using the JumpCloud API python library required by this project, you agree to the JumpCloud Terms of Service. The importer is not a component of the JumpCloud Service and is not required to be supported by JumpCloud. You are responsible for any risks with respect to, and for obtaining necessary rights to, any third-party software you download or install using the importer.

Table of Contents

Configuration Steps

Using the Importer

Troubleshooting

Clone this wiki locally