jamf/Setup-Manager
1
0
Fork 0
mirror of https://github.com/jamf/Setup-Manager.git synced 2026-08-11 23:41:44 +01:00
Code Issues 37 Actions Packages Projects Releases Wiki Activity

v1.4.6

Browse Source
This commit is contained in:
Armin Briegel
2026-06-23 08:35:39 +02:00
parent d2cfe7dd36
commit 005efccec5
2 changed files with 14 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
ChangeLog.md
View File

@@ -1,5 +1,12 @@
# Setup Manager - Change Log
## 1.4.6
(2026-06-22)
- fixed a potential crashing issue in log parsing (#217, #219)
- webhook urls are now abreviated in the log, unless the `DEBUG` key _in_ the `webhooks` dictionary is set to `true`
## 1.4.5
(2026-03-12)

8
Docs/Webhooks.md
View File

@@ -163,4 +163,10 @@ You can send multiple services per event:
### Webhooks in Debug mode
Webhooks are generally _not_ sent when DEBUG is set to true. However, if you set a `DEBUG` key to `true` _inside_ the webhooks dictionary to true, webhooks will be sent, even when global DEBUG is enabled.
Webhooks are generally _not_ sent when `DEBUG` is set to true. However, if you set a `DEBUG` key to `true` _inside_ the `webhooks` dictionary, webhooks will be sent, even when global `DEBUG` is enabled.
### Logging
Since the webhook URLs may contain codes you don't necessarily want to share, only the url scheme, host, and port are printed in the log, unless the `DEBUG` key inside the `webhooks` dictionary is set to `true`.
Note that the full URL for the webhook will always be visible in the profile, which will be visible to every user on the device in System Settings or with other tools. If you want to prevent the user seeing the webhook urls, you need to remove the Setup Manager profile after enrollment (using smart group scoping) or use a middleware server to indirectly talk with the webhook service.