Skip to content

Latest commit

 

History

History
76 lines (40 loc) · 5.89 KB

CHANGELOG.md

File metadata and controls

76 lines (40 loc) · 5.89 KB
Raw

jamf-upload Change Log

All notable changes to this project will be documented in this file. This project adheres to Semantic Versioning.

Known issues in latest version

jamf_pkg_upload.py uses an undocumented API for uploading packages to Jamf Cloud. As far as I know, this is the same API used by the Jamf Admin app. It is also the same method used by JSSImporter.

The HTTP responses from this API are unpredictable. You may see a 504 response, which indicates a Gateway Timeout error, but the package may well be delivered anyway. This is true whether uploading a new package or overwriting an existing one.

As the HTTP response cannot be guaranteed, I have not yet added the ability to write any package metadata such as category, manifest etc., which, as far as I can tell, must be supplied by a different API call after the package object has been uploaded. There is no predictable way to check that the package was successfully loaded unless we can guarantee that we are making our HTTP request to the same cluster node to which the package was uploaded.

I intend to add such functionality if changes are made to the Jamf Pro API so that these guarantees can be made.

Unreleased - TBD

Commits beyond the current tag will appear here.

0.3.0 - 2021-02-21

  • Moved jamf_upload.py to jamf_pkg_upload.py since we now have multiple scripts.

  • Added the jamf_script_upload.py script. This is used for uploading scripts to Jamf Pro. The option to include variables as in AutoPkg (%VARIABLE%) has been included.

  • Added the jamf_category_upload.py script. This is used for creating or uploading categories in Jamf Pro.

  • Added the jamf_computergroup_upload.py script. This is used for creating or uploading computer groups in Jamf Pro. The option to include variables as in AutoPkg (%VARIABLE%) has been included.

  • Added the jamf_ea_upload.py script. This is used for uploading script-based extension attributes to Jamf Pro. The option to include variables as in AutoPkg (%VARIABLE%) has been included. Other types of EA will be included in due course.

  • Added the jamf_policy_upload.py script. This is used for creating or uploading a policy in Jamf Pro. The option to include variables as in AutoPkg (%VARIABLE%) has been included.

  • Added the jamf_computerprofile_upload.py script. This is used for creating or uploading configuration profiles in Jamf Pro. Profiles can be supplied as either a payload plist or a complete mobileconfig file.

  • Added the jamf_computerprofile_sign.py script. This can be used for signing profiles.

  • Common functions have been moved into the jamf_upload_lib folder and included in each script to avoid too much repetition.

  • Examples in the _tests folder have been used for testing each of the upload scripts.

  • Added various working .jamf recipes, and associated templates and Self Service icons.

  • Switched from using Python's requests package to using curl for most functions. This allows a cookie to be set which should maintain a session throughout all requests in an AutoPkg run. Only jamf.pkg_upload.py retains a --requests option to use requests for uploading a package, and the --direct method also currently requires the requests package to be present in your python3 environment. The default upload method does not require requests.

  • Added jamf_api_tool.py for performing bulk search and delete tasks on API objects. This includes a Spruce-like function for deleting unused packages, smart groups, EAs and scripts. To use this, use ./jamf-api-tool.py --prefs /path/to/prefs --unused together with either --eas, --groups, --scripts or --packages. To delete the unused items, use the --delete parameter. This is currently interactive only. You can decide to delete all the unused items in one go, or go through each item in turn and get a y/n prompt.

  • Added sign_pkg.py which will sign a package.

  • Added sign_profile.py which will sign a mobileconfig file.

0.2.0 - 2020-07-24

  • Added the --direct method to jamf.pkg_upload.py, which allows package upload using the same method as performed via the Jamf Cloud GUI. This method has been ported here from python-jss. Packages are uploaded in chunks. The default chunk size is 1MB, but this can be altered using the --chunksize option. Many thanks to @mosen for porting this across.

  • Changed the requests option to upload via the data option rather than the files option. This prevents a problem of files larger than 2GB failing to upload due to a limitation in the ssl module (see psf/requests#2717 (comment)).

0.1.0 - 2020-07-03

  • Bundle-style packages are now handled properly, by zipping them before performing the upload to Jamf. If a zip file of the correct name is already present in the same folder as the package, it will not be recreated. Delete it if you need it to be remade.

This is developing into a testing script to accompany the AutoPkg processor JamfPackageUpload, so some debug modes are now available

  • You can now use the --curl option to switch to using the system curl rather than the Python requests module, in case this improves reliability, or just to perform tests. My initial tests have not shown any improvement in upload reliability, but YMMV.

  • You can set a timeout limit using the --timeout flag. This sets the timeout option in requests, or the --max-time option if using curl.

  • Different output verbosity levels (-v[v]) are available.

0.0.1 - 2020-06-26

Initial commit. Formerly a GitHub gist.