You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
If I update my containers automatically there may be issues during the update that I then only find out later. To avoid this, I update my containers manually. Nevertheless, I find it useful to know when updates are available. Therefore, I have Watchtower configured in "monitor only" mode and sending notifications to a Mattermost server. A scan is performed once per day.
My issue is as follows. Say one day Watchtower performs a scan and finds a container X with a new image version available with hash YYY. A notification is sent. Now let's say I'm on vacation for two weeks and unable to update the container. I will receive a notification every day until I do, which is annoying and unnecessary. One notification would suffice.
I may also not want to update a certain container, for whatever reason. Once again, receiving multiple notifications with the exact same information is unnecessary.
Describe the solution you'd like
My request: would it be possible for Watchtower to remember what notifications it has already sent (activated/deactivated by config argument, of course). That way, if a new image with hash YYY is available for container X, no matter how many scans are performed, only one notification is sent. Later a new-new image with hash ZZZ is available for X, send a notification again. But at least only one notification is sent per version.
Describe alternatives you've considered
Either accepting the notifications every day, or just rolling my own script to do what Watchtower does...
Additional context
No response
The text was updated successfully, but these errors were encountered:
Hi there! 👋🏼 As you're new to this repo, we'd like to suggest that you read our code of conduct as well as our contribution guidelines. Thanks a bunch for opening your first issue! 🙏
Is your feature request related to a problem? Please describe.
If I update my containers automatically there may be issues during the update that I then only find out later. To avoid this, I update my containers manually. Nevertheless, I find it useful to know when updates are available. Therefore, I have Watchtower configured in "monitor only" mode and sending notifications to a Mattermost server. A scan is performed once per day.
My issue is as follows. Say one day Watchtower performs a scan and finds a container X with a new image version available with hash YYY. A notification is sent. Now let's say I'm on vacation for two weeks and unable to update the container. I will receive a notification every day until I do, which is annoying and unnecessary. One notification would suffice.
I may also not want to update a certain container, for whatever reason. Once again, receiving multiple notifications with the exact same information is unnecessary.
Describe the solution you'd like
My request: would it be possible for Watchtower to remember what notifications it has already sent (activated/deactivated by config argument, of course). That way, if a new image with hash YYY is available for container X, no matter how many scans are performed, only one notification is sent. Later a new-new image with hash ZZZ is available for X, send a notification again. But at least only one notification is sent per version.
Describe alternatives you've considered
Either accepting the notifications every day, or just rolling my own script to do what Watchtower does...
Additional context
No response
The text was updated successfully, but these errors were encountered: