Skip to content

This PR introduces a new notification trigger provider for XMPP, allowing users to receive container update alerts via the XMPP protocol.#1058

Open
b09dan wants to merge 7 commits into
getwud:mainfrom
b09dan:infra/docker-publish
Open

Conversation

@b09dan

@b09dan b09dan commented May 10, 2026

Copy link
Copy Markdown

It implements the new Xmpp trigger class mimicking the structure of existing triggers and relies on the lightweight @xmpp/client dependency.

Changes Included

  • Added @xmpp/client dependency to app/package.json to handle the underlying protocol messaging.
  • Created Xmpp.ts under app/triggers/providers/xmpp/, exposing a configuration schema taking service, domain, user, password, and to properties.
  • Implemented messaging logic that properly connects, dispatches both single and batched notifications into chat stanzas, and gracefully disconnects per event.
  • Added Unit Tests in Xmpp.test.ts to validate the Joi configuration schema, data masking, and simulate @xmpp/client successful message dispatches.

Configuration Example

To use it, users will just need to set the variables such as:

WUD_TRIGGER_XMPP_MYBOT_SERVICE=xmpps://chat.example.com:5223
WUD_TRIGGER_XMPP_MYBOT_USER=user
WUD_TRIGGER_XMPP_MYBOT_PASSWORD=secret
WUD_TRIGGER_XMPP_MYBOT_TO=admin@example.com

b09dan and others added 7 commits April 9, 2026 01:26
Patch @xmpp/sasl to handle async mech.response() calls, which
are required for SCRAM-SHA-1 authentication. Add patch-package
to apply the fix during install and update the Dockerfile to
include patches in the build stage.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant