Jamf Pro and Classic API Changes:
+ Add support for Jamf Pro Classic API Bearer Tokens
+ Now uses Bearer Tokens to interact with the Classic API
+ Moved to using the Pro API for all endpoints where available
+ Created new helper methods for interacting with the Jamf Pro APIs and managing user authentication details
- Removed basic authentication support
Adding logging function for handling output to Policy Logs (level can be dynamically changed)
+ Numerous bug fixes
+ *Now* _actually_ Python3 ready...
+ Better (actual) support for macOS 11 and newer
+ Updated for Jamf Pro's new icon API
+ Adding logging function for handling output to Policy Logs (level can be dynamically changed)
+ Further improved launchctl functions
+ Additional code improvements
+ Fixed an issue when parsing through accounts passed via argument 4
+ Improved the comparison for local admins and protected admins (made this more reliable/safe)
+ Should prevent accounts with substrings of one another from matching
+ Added the ability to pass multiple files and/or directories to be collected
+ Removed mutual exclusion from the defaults, file, and directory switch
+ Added logic to parse switches/values passed from Jamf Pro when using multiple values in each passed Script Parameter
+ Moved archiving logic to a function/context manager
+ Using built-in plistlib to read plists now
+ Standardizing functions
+ Updated logic that determines the current console user to no longer use the old Python method
+ Python3 compatibility; allow setting of a custom Python binary path
+ Renamed script
+ Miscellaneous code improvements
Converted the Bash version into Python...because...why not? (Mainly a reason to learn more Python.)
This is a quick "Patch Management Framework" that I threw together quickly one day for a need (cough zoom cough).
Not a big fan of the built in patch "features" in Jamf Pro -- they leave a bit to be desired. This, more or less, combines the functionality of the two approaches (Standard Policies and Patch Policies) and makes them appear more "user friendly."
Initial version of a quick "Patch Management Framework" that I threw together quickly one day for a need (cough zoom cough).
Not a big fan of the built in patch "features" in Jamf Pro -- they leave a bit to be desired. This, more or less, combines the functionality of the two approaches (Standard Policies and Patch Policies) and makes them appear more "user friendly."
+ Added code to escape XML reserved characters
+ Added check for modern FileVault functionality
+ Added check for required Escrow Configuration Profiles
+ Added additional logging verbiage for Site Admins
