Closed JamesHillyard closed 1 month ago
@TwiN Makes sense, I have renamed teamsworkflow
to teams-workflows
and tested it still works. Thanks for the review!
@TwiN Looks like the text was expecting a broken teams emoji.. I must have changed it last minute and not updated the test. I've now fixed it and running go test -v .\alerting\provider\teamsworkflows\
results in all tests passing.
When can I use the new teams-workflows?
:warning: Please install the to ensure uploads and comments are reliably processed by Codecov.
Attention: Patch coverage is 92.00000%
with 6 lines
in your changes missing coverage. Please review.
Project coverage is 79.35%. Comparing base (
bb97397
) to head (7cc5bd3
). Report is 1 commits behind head on master.
Files with missing lines | Patch % | Lines |
---|---|---|
alerting/provider/teamsworkflows/teamsworkflows.go | 92.00% | 3 Missing and 3 partials :warning: |
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@JamesHillyard Great work & thank you for the contribution!
@TwiN not pushing you, but any idea when you'll create a new release including this code?
@liamjones-pw I usually let new features soak in latest for some time to give people time to report issues. If people are already using the feature and haven't reported any issues, I can create a release for it this weekend 👀
@liamjones-pw I just released v5.13.0
Summary
Fixes #820 by introducing a new
teams-workflows
alert compatible with Teams Workflows. Microsoft is deprecating the O365 webhook connector for Teams Workflows with MS Power Automate (Source: Microsoft DevBlog).The new Workflows require Microsoft Adaptive Cards and have a proprietary JSON format that means the old
teams
connector using a new Workflow URL will fail with this error:Breaking Changes
There are no breaking changes. The old
teams
alert still exists and will work with legacy O365 Webhook URLs.There are no breaking changes in configuring the
teams
andteamswebhook
alerts, meaning migration is simple.Migrating to new Teams Webhooks
End-users will need to make the following changes to migrate from the legacy
teams
alerts toteamswebhook
alerts:teams
(Inalerting
andendpoints[].alerts
) withteams-workflows
alerting.teams.webhook-url
(Nowalerting.teams-workflows.webhook-url
) with the new URL generated in the Teams WorkflowConfiguring the
teams-workflows
AlertMS Teams Configuration
Gatus Configuration
Remaining Issues
There are a few remaining issues, none are blockers to using this feature, but likely should be addressed in the future with further investigation.
Adaptive Card Version >1.5
Using an Adaptive Card higher than 1.4 (1.6 is latest) results in the message showing
This has been reported to AdaptiveCards (Report), but discussion around this issue seems very low.
Card Width
The cards do not show on teams as full-width. A StackOverflow post would suggest the width can be changed, but I wasn't able to get this to work.
Card Colour Strip
The red and green colour strip on the old teams cards at the top for triggered/resolved is not supported in Adaptive Cards. There are workaround options as identified in this Stack Overflow post but it doesn't look great.
Checklist
README.md
, if applicable.