-
-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
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
SECRETS file error when utilized in NOTIF mail TO option via 'diun.yml' #1133
Labels
Comments
Can you check within the diun container that the secret file exists and is not empty?
|
Sorry for the response delay. Yes, CAT of both ..username & ..password SECRETS respond w/ the expected values
Believe I 'hand-jammed' & utilized PRINTF as per...no /CR or /LF noted in the output |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Support guidelines
I've found a bug and checked that ...
Description
Using SECRET file in the TO parameter of the NOTIF for mail generates an error upon init. self-test.
Working:
Either instance below throws error:
or
Expected behaviour
System can re-use the existing SECRET, same as if typed in directly
Actual behaviour
Errors:
Steps to reproduce
Diun version
Latest (v4.26.0)
Docker info
Docker Compose config
Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: