# If a Slack webhook is not configured, all standard output should go to /tmp/autopkg.out. read /Users/ " $autopkg_user_account " NFSHomeDirectory | awk ' > /tmp/autopkg.out 2>/tmp/autopkg_error.out # using the autopkg_user_account_home variable.Īutopkg_user_account= "username_goes_here "Īutopkg_user_account_home= $(/usr/bin/dscl. # Note: The location is currently set to be automatically discovered # log_location – This should be the location and name of the AutoPkg run logs. For more information about this list, please see # recipe_list – This is the location of the plain text file being used to store # using the autopkg_user_account variable. # Note: The home folder location is currently set to be automatically discovered # autopkg_user_account_home – This should be the home folder location of the AutoPkg user account # autopkg_user_account – This should be the user account you're running AutoPkg in. # Adjust the following variables for your particular configuration. It’s also available from GitHub using the following link: The autopkg-conductor script is available below.
#SLACKER LOG IN MAC#
Instead, the information that the error log was empty will be logged to the logs stored on the Mac which is running autopkg-conductor. If no errors have been detected, the error log will no longer be sent to Slack. In the previous version of autopkg-conductor, the error log was sent to Slack even if no errors were detected. Instead, all logged output would be sent to Slack if a Slack webhook is set up.Īnother change to autopkg-conductor is to error reporting. If the slack_autopkg_processor variable is set, but isn’t one of the two expected values, the use of the processors is bypassed. If this variable is set correctly with the values specified in the script, it’ll enable autopkg-conductor to use the correct processor when reporting to a Slack channel. Home Assistant thejeffreystone 8/28/21 Home Assistant thejeffreystone 8/28/21. 5 Ways to Automate the Boring Stuff Read More. Automation thejeffreystone 9/13/21 Automation thejeffreystone 9/13/21. Site News thejeffreystone 1/26/22 Site News thejeffreystone 1/26/22. To accommodate using either the JamfUploaderSlacker or Slacker processor, I’ve added a new slack_autopkg_processor variable to autopkg-conductor. Easy Notifications with Alerts Read More. The message which appears in Slack should look similar to what is shown below:
JamfUploaderSlacker and Slacker both allow uploading information to a Slack channel using a webhook. For more details, please see below the jump.
#SLACKER LOG IN PRO#
These processors have emerged as a successor to JSSImporter, the original tool available to upload installer packages and other components to Jamf Pro using AutoPkg.Īs part of my work with Jamf Upload, I’ve also updated my autopkg-conductor script to allow the use of either Jamf Upload’s JamfUploaderSlacker AutoPkg processor or JSSImporter’s Slacker AutoPkg processors. As part of my preparations for Jamf’s planned authentication changes to the Classic API, I’ve been working more with the JamfUploader AutoPkg processors for Jamf Upload.
0 kommentar(er)
