Tags: alfhv/WebHooks
Tags
Made it possible to hook into the default WebHookSender instance and … …get called when a WebHook retries (in addition to succeeds, is gone, or fails). This enables for a variety of post-send processing scenarios where an implementation may want to take certain actions depending on whether a WebHook is retried.
Enforce mandatory properties in Azure Alert payload - Tag mandatory properties with Required.Always so JSON.NET enforces the requirement during (de)serialization - Fix a couple of comment typos on KuduNotification - Add required 'resourceRegion' property to AlertMessage1.json test content - Add AlertMessage3.json to validate change against sample payload in Azure docs - Add unit tests
Removed problematic references to System.IO required by older DataPro… …tection builds.
Added abstraction for making it simple to control how WebHooks are se… …nt. Now it is easy to enqueue messages into something like an Azure Storage Queue and also to control the format of what the actual WebHooks messages look like. This means that if you want the message format to be different then it's now easy to do. Added support for sending WebHooks directly to an Azure Storage Queue and also a mechanism for dequeing messages from the queue and then send out the WebHooks as normal. That allows for implementing highly scalable systems where the outgoing WebHooks are persisted in a queue and then can be sent from any number of queue client that poll for messages as they become available.
PreviousNext