Notifications stopped working shortly after 1.5 update and migrating triggers

[Crosis47]

So, I switched from WUD to Drydock a few weeks ago and it's been great. Everything was working fine until I moved to v1.5 and had toi migrate everything. I don't believe these have worked at all since and I've tried everything I can think of. I've even torn down the stack and rebuilt everything from scratch to make sure something in the volumes wasn't corrupt. I can't seem to figure out why but my notifications refuse to trigger for anything. Here is the env vars I am currently using, I have both of my notification triggers turned on in the UI for update available, applied, failed, etc.

DD_WATCHER_LOCAL_CRON=0 4 * * *
DD_WATCHER_LOCAL_JITTER=600000
DD_WATCHER_LOCAL_MAINTENANCEWINDOWTZ=America/New_York

DD_NOTIFICATION_SMTP_RESEND_HOST=smtp.resend.com
DD_NOTIFICATION_SMTP_RESEND_PORT=465
DD_NOTIFICATION_SMTP_RESEND_USER=resend
DD_NOTIFICATION_SMTP_RESEND_PASS=•••••
DD_NOTIFICATION_SMTP_RESEND_FROM=•••••
DD_NOTIFICATION_SMTP_RESEND_TO=•••••
DD_NOTIFICATION_SMTP_RESEND_TLS_ENABLED=true
DD_NOTIFICATION_SMTP_RESEND_TLS_VERIFY=true

DD_NOTIFICATION_DISCORD_DISCORD_URL=•••••

DD_ACTION_DOCKER_DIGEST-UPDATE_THRESHOLD=digest
DD_ACTION_DOCKER_DIGEST-UPDATE_PRUNE=true
DD_ACTION_DOCKER_DIGEST-UPDATE_AUTO=false

DD_ACTION_DOCKERCOMPOSE_TAG-UPDATE_BACKUP=true
DD_ACTION_DOCKERCOMPOSE_TAG-UPDATE_PRUNE=true
DD_ACTION_DOCKERCOMPOSE_TAG-UPDATE_COMPOSEFILEONCE=true
DD_ACTION_DOCKERCOMPOSE_TAG-UPDATE_ORDER=50
DD_ACTION_DOCKERCOMPOSE_TAG-UPDATE_AUTO=false

DD_SECURITY_SCANNER=trivy
DD_SECURITY_BLOCK_SEVERITY=NONE
DD_SECURITY_SCAN_CRON=30 4 * * *
DD_SECURITY_SCAN_JITTER=600000
DD_SECURITY_SCAN_CONCURRENCY=2

Here is an example of my label setup:

    labels:
      dd.display.icon: 'sh:sencho'
      dd.tag.include: '^\d+\.\d+\.\d+$$'
      dd.action.include: 'tag-update'
      dd.link.template: 'https://github.com/Studio-Saelix/sencho/releases/tag/v$${original}'
      dd.watch.digest: 'true'

I have tried using dd.notification.include labels to no avail but I didn't think that was necessary anyways when I am just notifying for all watched containers anyways. The notification triggers themselves are configured correctly as they work perfectly when testing from the UI. They just don't get triggered by anything. Does anyone see something I may have missed?

[Crosis47]

I have solved this issue. Apparently dd.notification and dd.action conflict with eachother and cannot be used on the same container. You must use one or the other as they are not additive but rather action will always take precedence and Drydockl will then ignore notification. I'll put in a bug report for this

[scttbnsn]

You nailed it, and thanks for going back and posting the root cause after you worked it out.

Tracking the fix in #494. Short version: the two labels get resolved as a list and the first match wins, so they collapse into one field before any trigger sees them. Fix is in progress for 1.6.