Skip to content

feat(rocketchat): support alias/emoji/avatar overrides and client TLS config - #1741

Open
mdiniz97 wants to merge 4 commits into
TwiN:masterfrom
mdiniz97:feat/rocketchat-alerting-provider
Open

feat(rocketchat): support alias/emoji/avatar overrides and client TLS config#1741
mdiniz97 wants to merge 4 commits into
TwiN:masterfrom
mdiniz97:feat/rocketchat-alerting-provider

Conversation

@mdiniz97

@mdiniz97 mdiniz97 commented Aug 1, 2026

Copy link
Copy Markdown

Summary

Extends the existing Rocket.Chat alerting provider (config/type registration was already scaffolded) with:

  • channel, alias, emoji, avatar overrides, matching Rocket.Chat's incoming webhook payload fields
  • client config (reusing the shared client.Config), so a webhook behind an internal/self-signed CA can be reached via client.insecure: true
  • Unit tests covering the new fields and group-override merging
  • Config parsing tests registering rocketchat alongside the other providers already covered in config_test.go
  • README section for alerting.rocketchat, including the untested-provider warning removal (confirmed working per discussion #1223) and a note that Rocket.Chat ignores the channel override unless "Allow to overwrite destination channel in the body parameters" is enabled on the incoming webhook integration

Test plan

  • go build ./...
  • go vet ./...
  • go test ./alerting/provider/rocketchat/... -v
  • go test ./config/... -v -run Alerting

…S config

Rocket.Chat incoming webhooks accept alias/emoji/avatar overrides and
may sit behind an internally-issued certificate, so extend the
provider's config and Send() to cover both.
Adds Validate/Send scenarios for the new fields and a GetConfig test
for group override merging, following the mattermost provider's test
shape.
Adds rocketchat to both alerting YAML parsing tests so the provider
is exercised alongside the others already covered there.
… override caveat

Confirmed working against a live Rocket.Chat server per
TwiN#1223 (comment),
so drop the untested-provider warning. Also documents that Rocket.Chat
ignores the channel override unless "Allow to overwrite destination
channel in the body parameters" is enabled on the incoming webhook.
@github-actions github-actions Bot added the feature New feature or request label Aug 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant