-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[docs] Fix indentation problems in processor examples #18115
Conversation
Pinging @elastic/integrations (Team:Integrations) |
💔 Build FailedExpand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
Are you sure these configuration snippets in the |
@kvch They original snippets do work, but they aren't "tidy" and and can't be pasted directly into an existing processors section without causing an error. I know this seems trivial, but invalid yaml files seem to trip people up quite a bit, and things like whitespace aren't always obvious. So our existing config files look like this:
If you paste one of our processor snippets into this config without adjusting the indentation, you get: So in #16696, I suggested that we fix the regular config files (filebeat.yml etc) rather that all the docs, but @exekias pointed out that we use spaces everywhere else so it would be awkward to not use them under processors. I wasn't expecting there to be so many changes but since all the reference yaml files are generated from the same source, it wasn't as much work as it seems. |
Closes #16696
Makes docs and reference.yml files consistent with how processors are defined in the beats.yml files. This change makes it easier for users to copy/paste and avoids the situation where they might create invalid yaml.
Also fixes a few other minor issues I found while going through the processor docs.
TODO: