Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Extreme validation #15

Closed
jvassev opened this issue Jul 3, 2018 · 0 comments
Closed

Extreme validation #15

jvassev opened this issue Jul 3, 2018 · 0 comments
Labels
enhancement New feature or request

Comments

@jvassev
Copy link
Contributor

jvassev commented Jul 3, 2018

Running fluentd with --dry-run only checks the general config format. If a plugin is misconfigured it will cause the daemon to exit.

Find a way to validate config by actually running fluentd with the config file being validated and catch any errors.
jvassev added a commit that referenced this issue Jul 3, 2018
@jvassev
Extreme validator by means of 'just_exit' plugin
f5fb9aa 
Insread of just --dry-running the config for a namespace, a normal
fluentd process is now started. A <source> of type @just_exit is added
to the expanded user config which just does exit(0). If any plug-in
(filter or output) is misconfigured then fluentd exits immediately after
encountering the error.

This helps ignore namespaces with misconfigured sensitive plugins like
S3 or logzio - or any other plugin that requires credentials to work.

See #15 for more info.
@jvassev jvassev added the enhancement New feature or request label Jul 5, 2018
@jvassev jvassev closed this as completed Jul 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jvassev