Webhook payload runon Azure vs Hybrid worker

Ronald Foppen 0

I am working with azure automation, triggered by webhooks.

Typically this runs directly on Azure and works fine, the webhook data payload is received and handled as a PSCustomObject.

I now need to run the same on a Hybrid Worker because of a OnPrem requirement. When updating the webhook to run on a HW, and sending exactly the same payload, the web hook data is treated as a System.String.

This is obviously causing some challenges; I could look at parsing the string into individual elements again, but that is a PITA.

Any thoughts on why there is a difference on how the webhook data is treated? Or better, how to resolve it.

I've used the very simple example here: https://learn.microsoft.com/en-us/azure/automation/automation-webhooks?tabs=portal#use-a-webhook

1 answer

Stanislav Zhelyazkov 22,101 Reputation points MVP

2024-07-15T05:36:57.79+00:00

Hi,

I do not know why is different as I haven't used hybrid workers but the easiest way to solve it is to treat the input as json and convert it to PSObject (ConvertFrom-Json). In fact the example does that for the request body.

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
Please sign in to rate this answer.
Ronald Foppen 0 Reputation points

2024-07-15T15:26:08.5466667+00:00

Thanks for the suggestion; that's actually exactly the example I followed for my testing. I've added two webhooks, one running on Azure, the other one on a Hybrid Worker.

Sending the same JSON payload. Result is wildly different.

The Hybrid Worker one outputs the webhookdata as a System.String; which (obviously) won't work when doing the ConvertFrom-JSON

$Names = @( @{ Name="Hawaii"}, @{ Name="Seattle"}, @{ Name="Florida"} ) $body = ConvertTo-Json -InputObject $Names $testwebhookuriAZURE = "https://xxx.azure-automation.net/webhooks?token=xxx" $testwebhookuriHW = "https://xxx.azure-automation.net/webhooks?token=xxxx" Invoke-RestMethod -Method POST -Uri $testwebhookuriAZURE -Body $body Invoke-RestMethod -Method POST -Uri $testwebhookuriHW -Body $body

Running on Azure outputs as PSCustomobject, and everything works as expected

Stanislav Zhelyazkov 22,101 Reputation points MVP

2024-07-16T05:38:37.53+00:00

ok. As I have mentioned I do not know why there is a difference as I do not use it but shouldn't converting it from JSON to PS object workaround the issue for hybrid workers?

Ronald Foppen 0 Reputation points

2024-07-16T08:36:18.4866667+00:00

The data is when using the Hybrid Works is not valid a JSON; hence nothing to (easily) convert.

I am now experimenting with regex removing the parts I do not need, leaving only the requestbody in a format which I can do a ConvertFrom-Json

Main point still remains why the data becomes a string on the HW instead of staying a psobject

Anyways, thanks for thinking along!

{WebhookName:onpremhook,RequestBody:[\r\n {\r\n "Name": "Hawaii"\r\n },\r\n {\r\n "Name": "Seattle"\r\n },\r\n {\r\n "Name": "Florida"\r\n }\r\n],RequestHeader:{Accept-Encoding:gzip,Host:1f7b5302-3e30-4141-972a-91d03321e62d.webhook.eus.azure-automation.net,User-Agent:Mozilla/5.0,x-ms-request-id:7cadfc0f-5b36-47fd-bca4-470a3aad2567}}
Sign in to comment

Share via

Webhook payload runon Azure vs Hybrid worker

1 answer