Customize watchers and triggers on a container(group)-basis (using category labels)

[MielsvS]

It took me quite some effort to configure WUD initially, but very happy with it! Thanks!

The past couple of weeks I did realize I had several needs that can't seem to be addressed in WUD yet. Wanted to let you in on my thoughts, perhaps you can use it as input for future versions :).

Here some use cases for 3 different categories of containers I have distinguished:

1. Critical
   Should never auto-update, but I do want to be informed of updates. Since updating those requires testing etc. I don't want frequent notifications (once a month seems fine) and I want to ignore minor updates
2. Normal
   I am willing to auto-update those and I want a notification of available updates (but preferable when the update has been performed). I want the updates to be performed on every thursday night: When something goes wrong the impact is less, since there are less users on friday and I tend to have more time available on fridays. Plus since I perform updates weekly there shouldn't be many failed updates at the same time
3. Vulnerable
   These containers are exposed to the internet, and I want them updated ASAP (every night)

More use cases:

4. I want newly added containers to be watched, even if I have forgotten to add any WUD-labels (see my previous post here for more info). But I don't want them to be updated unless I have explicitly allowed that. Currently there is no way to auto-start a trigger but to let it skip containers that have no trigger.include or trigger.exclude
5. I want to change my update policy for an entire category of containers (for example: excluding containers for a new trigger I built). Currently I have to edit the docker compose for many containers separately. That's a pain in the *** and prone for mistakes.
6. I only want 1 container (of the 30) to auto-update. Currently I have to edit all-but-this-one container configs to achieve that.

A possible solution I came up with:

• define (custom) category-labels within a container
• configure watchers and triggers to be active on certain categories only
• you should be able to define multiple categories per container/watcher/trigger.
  Regarding wachters/triggers: Would be great if you could use operators (like AND / OR / NOT). Plus a "category = none" option.

[CodingGhost]

I would also love these features!
especially this one:

I only want 1 container (of the 30) to auto-update. Currently I have to edit all-but-this-one container configs to achieve that.

some config for a trigger like default-include-all=false would even be enough for this, as the trigger.include exists. I dont even understand what trigger.include does because everything is included by default anyways.

[fmartinou]

Feature merged via #1293! The WUD_WATCHER_{name}_EXCLUDE configuration option is now available for Docker watchers. It will be included in the next release. Thanks for the feedback!