CrazyMax
CrazyMax
@razvan-moj Yes we could allow notifiers per containers through labels/annotations.
We can add a `watch.override` opt: ```yaml watch: override: watch_repo: true notify_on: update max_tags: 100 include_tags: - ... exclude_tags: - ... ```
`watch.defaults` might be a better naming actually.
@Timmiej93 > At scheduled moment, send a notification of every watched container that has an attribute "update available", with a value of true or false It defeats the purpose of...
> What does the `unchange` attribute currently do? This means there is no update available for the image that has been scanned which seems what you want. For a webhook...
That was just an example. Only `new` and `update` are available atm.
Sure we can add the `unchange` state to the [`notify_on` opt](https://crazymax.dev/diun/providers/file/#yaml-configuration-file). I'm fine with it.
@hgl > I wonder if you fancy something like this: > `swarm.cronjob.update-services=nginx db` > The listed services are updated (using service update --force) if the command returns successfully. This seems...
Hi guys, I did some tests on my side and it appears that this could be due to the way the tasks on the Swarm side are managed. Maybe linked...
@djmaze Yes I'm aware of this feature. That looks promising and I think it will benefit for the global mode support (and fix this issue).