We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chart: v0.1.26 App: v0.2.3
Let's say we are using this example watchdog email config in the values.yaml:
watchdogConfig: ... emailEnable: "true" emailAccount: "[email protected]" emailPassword: "password1234" emailRecipients: "[email protected]" emailSmtpPort: 587 emailSmtpServer: "smtp.example.com" ...
This will result in this service entry in the GUI (Settings > Watchdog > Service notification ) after deploying the Helm Chart:
mailtos://[email protected]:[email protected]?to=[email protected]&format=markdown
If the "Test Service" button is clicked for this service this error message will appear
and the following entry will be added to the log of the vui-watchdog pod:
dispatcher_apprise.py[59]->send_msgs - ERROR No APPRISE config found
Additionally, no email will be send.
This behavior also occurs with messages triggered by velero events.
If the first "@" of the service entry is replaced with "%40" everything works as expected: The email will be send and no error messages will be shown:
mailtos://user%40example.com:[email protected]?to=[email protected]&format=markdown
Triggered notifications are also sent now.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Used config
Chart: v0.1.26
App: v0.2.3
Let's say we are using this example watchdog email config in the values.yaml:
This will result in this service entry in the GUI (Settings > Watchdog > Service notification ) after deploying the Helm Chart:
Problem description
If the "Test Service" button is clicked for this service this error message will appear
and the following entry will be added to the log of the vui-watchdog pod:
Additionally, no email will be send.
This behavior also occurs with messages triggered by velero events.
Workaround
If the first "@" of the service entry is replaced with "%40" everything works as expected: The email will be send and no error messages will be shown:
Triggered notifications are also sent now.
The text was updated successfully, but these errors were encountered: