Migrate MS Teams webhooks to Power Automate
Microsoft recently announced to retire the Office connectors in Microsoft Teams to deliver content from third-party services into a Teams channel.
Microsoft recently announced to retire the Office connectors in Microsoft Teams to deliver content from third-party services into a Teams channel.
For a few of our customer projects, we use Tideways to spot performance bottlenecks and get real-time error detection alerts.
As a bonus, Tideways can track deployment events to compare performance and failure rates before and after the deployment.
In a recent attempt to automate a few things even more, I was looking for a way to post messages to our Mattermost instance via the Incoming Webhook feature of Mattermost. I did a quick search on Packagist for Mattermost client libraries and as it turns out there a quite a few. I picked the thibaud-dauce/mattermost-php package simply because it was the first match ;)
In our "old" Jenkins set-up things were simple: The Jenkins master and Satis were running on the same host thus Jenkins could easily invoke Satis via a command-line call. Unfortunately GitLab does not allow that. The only option which is currently available in GitLab is to trigger Satis via a webhook. Neither Satis itself or Satisfy which we actually use provide support for webhooks. Thus we extended Satisfy with a simple controller which invokes the Satis cli command. Definitely not the best solution but it works for us.