Pushover Notification Customization of sound and priority

[michaelkrieger]

Behaviour

Pushover always sends with the default sounds but in many cases this can be delivered silently or with a different priority.

Steps to reproduce this issue

N/A

Expected behaviour

The API calls for:

priority - send as -2 to generate no notification/alert, -1 to always send as a quiet notification, 1 to display as high-priority and bypass the user's quiet hours, or 2 to also require confirmation from the user

sound - the name of one of the sounds supported by device clients to override the user's default sound choice (string)

These should be customizable through configuration or the pushover environment variables.

Actual behaviour

These are not customizable and it will always play the default sound and priority

Configuration

• Diun version : 4.20.1
• Platform (windows/linux) : linux
• System info (type uname -a) : Debian 11

[wsc96]

This would be great.

[tushev]

@crazy-max in

diun/internal/notif/pushover/client.go

Line 66 in 5d58380

Priority: c.cfg.Priority,

and

diun/internal/model/notif_pushover.go

Line 9 in 5d58380

Priority int `yaml:"priority,omitempty" json:"priority,omitempty" validate:"omitempty,min=-2,max=2"`

there's already a Priority.

Is it somehow possible to set that value in docker-compose?

The docs say nothing about it.

[fanaticDavid]

Priority definitely works, even if it's not documented. I'm using the configuration file diun.yml:

notif:
  pushover:
    token: [REDACTED]
    recipient: [REDACTED]
    priority: -2
    templateTitle: "{{ .Entry.Image }} released"
    templateBody: |
      Docker tag {{ .Entry.Image }} which you subscribed to through {{ .Entry.Provider }} provider has been released.

[tushev]

@fanaticDavid thank you for sharing! Will try diun.yml.

[tushev]

Thanks!