Add dynamic injection of HTTP headers for notifications #17

New Issue

2025-04-05T17:43:22Z

CyberShell commented

2025-04-05 17:43:22 +00:00

There should be a method to allow dynamic injection of HTTP notification headers for notifications. This should be via the CLI, and via the configuration file, using sane path scheme.

  http:
    ntfy:
      url: https://ntfy.domain.tld/topic
      method: POST
      headers:
        Content-Type: application/json
        Priority: max
        Authorization: needs to be generated dynamically

On the CLI, the following flag should be global:

--notificationHttpHeaderOverrides "ntfy.Authorization=$(command to generate authorization header)"

The structure of the data is as follows:

"[id].headerKey=headerValue"

External directive support could also be added to the notifications.http.[id].Headers object.

There should be a method to allow dynamic injection of HTTP notification headers for notifications. This should be via the CLI, and via the configuration file, using sane path scheme. ```yaml http: ntfy: url: https://ntfy.domain.tld/topic method: POST headers: Content-Type: application/json Priority: max Authorization: needs to be generated dynamically ``` On the CLI, the following flag should be global: ``` --notificationHttpHeaderOverrides "ntfy.Authorization=$(command to generate authorization header)" ``` The structure of the data is as follows: ``` "[id].headerKey=headerValue" ``` External directive support could also be added to the `notifications.http.[id].Headers` object.

CyberShell changed title from ~~Allow dynamic injection of HTTP notification headers for notifications~~ to Add dynamic injection of HTTP headers for notifications

2025-04-08 17:13:25 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: CyberShell/backy#17