Summary
Policy details include the scripts, so you can read what a policy does before running it.
That is the difference between this and clicking through the Jamf console: getPolicyDetails returns the scope, the attached packages and the full script content in one answer. Destructive actions ask first, and JAMF_READ_ONLY exists for the case where you want no chance of a write at all.
What it is
A server covering Jamf Pro across computers, mobile devices, policies, scripts, configuration profiles, packages and groups, with read-only resources and prompt templates for the common workflows.
What you get
- searchDevices, getDeviceDetails, getDevicesBatch, checkDeviceCompliance and updateInventory
- listPolicies, searchPolicies and getPolicyDetails — including the scope and the full text of the scripts and packages attached to a policy
- executePolicy and deployScript, both behind a confirmation step
- getScriptDetails with parameters, notes and OS requirements
- Configuration profiles: list, search, get details, deploy and remove
- Packages: list, search, details, deployment history and which policies use a given package
- Computer groups: list, details, members, search, create and update static groups, delete
- Mobile devices: search, list, details, inventory update, group listings, and sendMDMCommand for lock, wipe and passcode clearing
- Resources for computer and mobile inventory, compliance, storage and OS-version reports
Requirements
Node, built from the repository. Create an API Role and API Client in Jamf Pro, then set JAMF_URL, JAMF_CLIENT_ID and JAMF_CLIENT_SECRET. JAMF_READ_ONLY=true blocks every modification if you want to look without touching.