Skip to main content

NATS

The NATS trigger publishes container update events as JSON payloads to subjects on NATS messaging servers, enabling cloud-native streaming and microservice orchestration.

⚙️ Configuration Variables​

WUD_TRIGGER_NATS_{trigger_name}_SERVERS
Requiredstring

NATS server URL(s)

Allowed values:Comma-separated list of NATS server URLs (e.g. `nats://127.0.0.1:4222` or `tls://demo.nats.io:4443`)
WUD_TRIGGER_NATS_{trigger_name}_DISABLETITLE
Optionalbooleandefault: false

Whether to omit the notification title in payload

WUD_TRIGGER_NATS_{trigger_name}_NKEY
Optionalstring

NATS NKey seed for public-key authentication

WUD_TRIGGER_NATS_{trigger_name}_PASSWORD
Optionalstring

NATS basic authentication password

WUD_TRIGGER_NATS_{trigger_name}_SUBJECT
Optionalstringdefault: wud.container

NATS subject to publish container update messages to

WUD_TRIGGER_NATS_{trigger_name}_TOKEN
Optionalstring

NATS authentication token

WUD_TRIGGER_NATS_{trigger_name}_USER
Optionalstring

NATS basic authentication username

info

This trigger also supports all common trigger configuration options (such as thresholds, scheduling, and batching).

🚀 Examples​

Publishing to NATS Subject​

services:
  whatsupdocker:
    image: getwud/wud
    environment:
      - WUD_TRIGGER_NATS_CLUSTER_SERVERS=nats://nats1:4222,nats://nats2:4222
      - WUD_TRIGGER_NATS_CLUSTER_SUBJECT=docker.updates
      - WUD_TRIGGER_NATS_CLUSTER_TOKEN=s3cr3tt0k3n