Allow for custom notification message about diun

[crazy-max]

@TUISTERa Yes I've planned to add this through a simple template. Keep you in touch.

[TUISTERa]

If you can add custom tags In message the botname can be irrelevant. For example #s1 #plex , #s2 #homeassistant etc...

…

On Wed, Jan 20, 2021, 5:57 AM sintax ***@***.***> wrote: Would this also include the ability to provide a custom name to the bot for example on discord it shows up as DIUN[bot], i'd like to be able to customize the name such as DIUN-Server1name, DIUN-Server2Name so both of my monitored servers can alert the same channel and i can differentiate them. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#64 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAL2P5RDDLDUFJTPKFPKNS3S2ZIEDANCNFSM4MLO3VUA> .

[bigjdunham]

Bump for inclusion of this, especially the ability to create custom headers for email and pushover notifications.

[TUISTERa]

Hello, Do you have any plans for adding this? At least i want to add a "#duin" at the end of the message , for filtering purpose at my telegram notifications...

[sintaxx]

Would this also include the ability to provide a custom name to the bot for example on discord it shows up as DIUN[bot], i'd like to be able to customize the name such as DIUN-Server1name, DIUN-Server2Name so both of my monitored servers can alert the same channel and i can differentiate them.

[laurentlbm]

It would be very helpful if notifications included a link to the change log of the release. Unfortunately, that info doesn't seem readily available on docker hub, so a custom message with a link to the GitHub/website of the image would be an ok compromise.

[crazy-max]

Working on it for the next release. You will be able to customize the title and body of the message for each notification providers. This will be limited to markdown and html rendering atm. The JSON or ENV output will remain immutable.

[crazy-max]

You can test this feature with crazymax/diun:edge. Documentation for each notifiers can be found here.

Example with mail:

watch:
  workers: 20
  schedule: "0 */6 * * *"
  firstCheckNotif: false

notif:
  mail:
    host: localhost
    port: 25
    ssl: false
    insecureSkipVerify: false
    from: [email protected]
    to: [email protected]
    templateTitle: |
      {{ .Entry.Image }} released
    templateBody: |
      Docker tag {{ if .Entry.Image.HubLink }}[**{{ .Entry.Image }}**]({{ .Entry.Image.HubLink }}){{ else }}**{{ .Entry.Image }}**{{ end }}
      which you subscribed to through {{ .Entry.Provider }} provider has been {{ if (eq .Entry.Status "new") }}newly added{{ else }}updated{{ end }}.
      This image has been {{ if (eq .Entry.Status "new") }}created{{ else }}updated{{ end }} at
      <code>{{ .Entry.Manifest.Created.Format "Jan 02, 2006 15:04:05 UTC" }}</code> with digest <code>{{ .Entry.Manifest.Digest }}</code>
      for <code>{{ .Entry.Manifest.Platform }}</code> platform.

providers:
  docker:
    watchByDefault: true

Documentation about notification template: https://github.com/crazy-max/diun/blob/master/docs/faq.md#notification-template