tigattack/VeeamNotify v2.0.0

on GitHub

🎉 What's New

• HTTP notifications support
  • Supports GET and POST methods.
  • Job data will be included in request body if method is POST.
  • GET can be used to 'ping' a monitoring tool such as Uptime Kuma.
• Fixed various issues with Telegram service.
• Updated config schema — ⚠️ Includes breaking changes. See Breaking Changes section below.
  • Define required keys for each service.
  • Updates default thumbnail URL (image has not changed).

⚠️ Breaking Changes

• Veeam Backup & Replication >= 12 is now required.
  • Prior to this release, VBR 11 was the minimum version.
• Configuration (conf.json):
  • All services must have an enabled key. Only services with "enabled": true will be notified. Example:

     "services": {
         "discord": {
             "enabled": true,
             "webhook": "https://discord.com/....",
             "user_id": "123456789"
         },

  • MS Teams user_name property is renamed to display_name.

Miscellaneous

• User agent for requests to notification services is now VeeamNotify; PowerShell/<PS major.minor> (e.g. VeeamNotify; PowerShell/5.1).
• Improve config schema validation.
• Improved installer script and Veeam config deployment script (for configuring jobs to use VeeamNotify).
• Lots of miscellaneous refactoring and behind-the-scenes improvements to code maintainability and readability, error handling, logging, and minor performance improvements.

Full Changelog: v1.1.2...v2.0.0