Microsoft Teams connector webhook URL format changed

[kevinlul]

This causes teams:// URLs to fail as well as directly pasting the webhook URL for the Watchtower Teams integration, since it tries to parse the URL and use shoutrrr anyway.

[piksel]

This is fixed in v0.4.0 and should be included in the next watchtower release.

[papanito]

I guess docu should be updated as well: https://github.com/containrrr/shoutrrr/blob/main/docs/services/overview.md

[piksel]

Yeah, and I just noticed that they actually explain what the fields are above, documentation I wasn't able to find anywhere before.

[papanito]

Yeah, and I just noticed that they actually explain what the fields are above, documentation I wasn't able to find anywhere before.

I actually don't find this documentation either.

[piksel]

This was addressed in #167, but the docs still contain some incorrect information:
https://containrrr.dev/shoutrrr/latest/services/teams/

Keeping this open until it's fixed.

[LanJosh]

Yeah, and I just noticed that they actually explain what the fields are above, documentation I wasn't able to find anywhere before.

I actually don't find this documentation either.

I can't seem to find this documentation either, what is the field supposed to be?

[piksel]

@LanJosh host. It's in the top Attention box in the docs:
https://containrrr.dev/shoutrrr/latest/services/teams/

If you are referring to how to get it, it's the hostname that your teams webhook URL starts with: xxxxxx.webhook.office.com

You can follow the guide in the teams docs to create a new one if you don't have one with the correct host.

---

The thing we referred to above regarding the docs was the fact that the image in the issue post actually explained what all of the fields in the magic webhook URLs were. We used to refer to them as tokenA, tokenB etc. since it wasn't clear what they were.

[igorcezar]

Since the webhook URL format changed, shouldn't this line also be able to set /webhookb2/?

shoutrrr/pkg/services/teams/teams_config.go

Line 106 in 23170b8

"https://%s/webhook/%s@%s/IncomingWebhook/%s/%s",

It doesn't work for new URL format because it will build the url as https://<tName>.webhook.office.com/webhook/token..., which doesn't exist.

[piksel]

@igorcezar both the webhookb2 and webhook URLs worked in the integration tests (that's why it wasn't caught earlier). nevertheless, it was wrong and has been fixed in #188