Skip to content

Deploy in GitHub

Jump to bottom
Ryan Ball edited this page Jun 28, 2023 · 1 revision

Note: Charges may apply when running any Action in GitHub. 😉

Configure the GitHub Action

  1. In your forked jamf-pro-notifications-alerter repository click to "Settings" in the top navigation bar.
  2. Click "Actions" > "General" in the left sidebar and ensure one of the "Allow actions..." options are selected under "Actions permissions".
  3. Click "Save" at the bottom of the page.
  4. Click "Actions" in the top navigation bar, you should see "jamf-pro-notifications-alerter Job" in the left sidebar.

Configure Environmental Variables

  1. In your forked jamf-pro-notifications-alerter repository click "Settings" in the top navigation bar.
  2. Click "Secrets and variables" in the left sidebar, then click "Actions".
  3. Create Secrets/Variables for for any of the Jamf Pro URL(s), API User(s), API Password(s) and Slack webhook(s) you wish to pass as variables. We highly recommend using secrets for all API Passwords which will be obfuscated in the job output.

Note: Our sample jamf-pro-notifications-alerter.yml file assumes you've set API_PASS and SLACK_WEBHOOK as environmental variables, so you don't need to pass those at the command line.

Reference: GitHub Actions - Variables

Complete the Project

The sample jamf-pro-notifications-alerter.yml file is configured to show you how to get notifications two Jamf Pro servers. You can modify this for your number of Jamf Pro servers replacing the placeholder variables after the --url and --password options with the variable/secret names you previously created.

You can then schedule this pipeline to run on your preferred schedule using GitHub's guide.

Clone this wiki locally