-
Notifications
You must be signed in to change notification settings - Fork 330
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
Logging Operator should check semantics as well #1460
Comments
Somewhat related issue: #1432. |
Yes, the intent is the same! |
We could however add validation in the operator itself so that it catches output references that do not exist in the config. The fluentd config builder does this already. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! |
this can only be implemented for syslog-ng currently |
Describe the bug:
If there is a syslog-ng configuration change which is syntactically correct, but semantically not (i.e., unknown destination/output) then the logging-operator's configcheck does not catch it.
Expected behaviour:
The configcheck should check for semantics as well during the validation.
Steps to reproduce the bug:
Follow the official quick start guide but the output should refer to something undefined.
Additional context:
Environment details:
/kind bug
The text was updated successfully, but these errors were encountered: