Triggers

Triggers are responsible for performing actions when a new container version is found.

Triggers are enabled using environment variables.

DD_TRIGGER_{{ trigger_type }}_{{trigger_name }}_{{ trigger_configuration_item }}=XXX

Common trigger configuration

All implemented triggers, in addition to their specific configuration, also support the following common configuration variables.

Notification Rules

Notification rules control which events fire which triggers. Each rule corresponds to an event type and has an enabled flag and an optional list of trigger IDs.

Dispatch behavior:

• update-available -- for backward compatibility, when its trigger list is empty all triggers fire (existing behavior is preserved). Once you assign specific triggers, only those fire.
• update-applied, update-failed, security-alert -- these require explicit trigger assignments. They are enabled by default but will not fire any trigger until you add trigger IDs to their rules.
• agent-disconnect -- disabled by default. Enable it and assign triggers to receive disconnect alerts. This event always fires regardless of the threshold setting.

Rules are managed via GET /api/notifications and PATCH /api/notifications/:id (update enabled and/or triggers fields), or through the Notifications view in the UI.

Event Types

Beyond the classic update-available event, triggers can fire on additional events:

• update-applied -- fires after a container is successfully updated by a Docker or Docker Compose trigger. Useful for audit or confirmation notifications.
• update-failed -- fires when an update fails or is rolled back. Carries the container name and error message.
• security-alert -- fires when the Update Bouncer detects critical or high vulnerabilities during a pre-update scan. Includes a vulnerability summary.
• agent-disconnect -- fires when a remote agent loses its connection. This event skips threshold checks (always fires).

Template Variable Reference

Template strings use ${expression} placeholders. Drydock provides two sets of variables depending on the trigger mode.

Simple mode variables

Legacy aliases (deprecated): id, name, watcher, kind, semver, local, remote, link.

Batch mode variables

Legacy alias (deprecated): count (same as containers.length).

Expression syntax

Inside ${...} you can use:

• Property paths -- container.updateKind.kind
• Method calls -- local.substring(0, 15) (see allowed methods below)
• Ternary -- container.result.link ? container.result.link : "no link"
• Logical AND -- container.result && container.result.link
• String concatenation -- "Version: " + container.updateKind.remoteValue
• String and number literals -- "hello", 42

Allowed string methods: substring, slice, toLowerCase, toUpperCase, trim, trimStart, trimEnd, replace, split, indexOf, lastIndexOf, startsWith, endsWith, includes, charAt, padStart, padEnd, repeat, toString.

Examples

services:
  drydock:
    image: codeswhat/drydock
    ...
    environment:
      - DD_TRIGGER_SMTP_GMAIL_SIMPLETITLE=Container $${container.name} can be updated
      - DD_TRIGGER_SMTP_GMAIL_SIMPLEBODY=Container $${name} can be updated from $${local.substring(0, 15)} to $${remote.substring(0, 15)}

docker run \
  -e 'DD_TRIGGER_SMTP_GMAIL_SIMPLETITLE=Container ${container.name} can be updated' \
  -e 'DD_TRIGGER_SMTP_GMAIL_SIMPLEBODY=Container ${name} can be updated from ${local.substring(0, 15)} to ${remote.substring(0, 15)}'
  ...
  codeswhat/drydock