Replies: 1 comment 1 reply
-
|
Hi, do you want that prefix to be in the notification title or would you rather want additional, optional labels that will be added to the notification body? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I’m running doco-cd on multiple machines and rely heavily on the notification system.
Right now, all notifications look the same, which makes it difficult to see which server triggered the event.
Idea:
Add an optional configuration field to include a server prefix (e.g. hostname, custom label) in every notification message.
A simple static prefix in the config would already be very helpful e.g. APPRISE_HOSTNAME
And a second Idea:
Right now, every notification includes metadata like revision, job ID, and repo.
For me (and maybe others too) that level of detail isn’t needed.
I only need the action type (deploy, failure, etc.) and the stack name.
A configuration option to enable/disable notification fields would solve this cleanly e.g. APPRISE_INCLUDE_METADATA
Would love to hear your thoughts!
Beta Was this translation helpful? Give feedback.
All reactions