- as discussed in https://github.com/aspnet/WebHooks/pull/210#discussion_r158419203
- `message` -> `queueMessage` where main change caused a conflict
- also
- `ack` -> `success`
- `asm[s]` -> `assembly` / `assemblies`
- `cnt` -> `i` except in 2 places where `count` was better
- `count` -> `data` first in one of those cases
- `combo` -> `combinedBytes`
- `invalidFiltersMsg` -> `invalidFiltersMessage`
- `se` -> `storageException`
- leave `config` alone; exposed publicly e.g. `Microsoft.AspNet.WebHooks.Config.WebHooksConfig`
nits: accept lots of VS suggestions
- more `var` especially
- move to MSBuild v15.0
- move to StyleCop.MSBuild v5.0.0
- stable release that supports C#6, not just `nameof(...)`
- move test output path beside, rather than under, regular output path
- workaround NuGet/Home#6001
- `\$(Configuration)\Test` -> `\Test\$(Configuration)`
- quiets builds down significantly
- add AppVeyor configuration and status badge
- disable Travis builds for now
- ignore launchSettings.json files
config.InitializeReceiveStripeDirectWebHooks();
When using this mode, the WebHook URI must have a scheme of 'https' and contain a 'code' query parameter with a value between 32 and 64 characters, for example:
http://<host>/api/webhooks/incoming/stripe?code=83699ec7c1d794c0c780e49a5c72972590571fd8
The code must match the value set in the 'MS_WebHookReceiverSecret_Stripe' application setting, for example:
<add key="MS_WebHookReceiverSecret_Stripe" value="83699ec7c1d794c0c780e49a5c72972590571fd8" />
Henrik
Add MS_WebHookStripeInTestMode to execute custom StripeWebHookHandlers for test events ('evt_00000000000000')
Add StripeEvent and StripeEventData classes
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.