-
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
Cherry-pick #20898 to 7.x: Avoid generating incomplete configurations in autodiscover #20919
Conversation
…0898) Handle errors when configuration unpacking fails. In principle this can only happen when some variable is missing, because configuration has been previously parsed as YAML. Errors on unpacking were previously ignored. When a variable is missing, this is clearly logged at the debug level. This changes the behaviour, previously an incomplete configuration was generated on this case. (cherry picked from commit 99fd545)
Pinging @elastic/integrations-platforms (Team:Platforms) |
💔 Tests 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
|
jenkins run the tests please |
Cherry-pick of PR #20898 to 7.x branch. Original message:
What does this PR do?
Handle errors when configuration unpacking fails. In principle this can
only happen when some variable is missing, because configuration has
been previously parsed as YAML. Errors on unpacking were previously
ignored.
When a variable is missing, this is clearly logged at the debug level.
This changes the behaviour, previously an incomplete configuration was
generated on this case.
Why is it important?
To detect problems with incomplete configuration earlier and improve feedback in logs
when a variable is missing in event.
Since #18979 this error is more frequent, as a legit configuration for containers produces
errors with pod events that don't contain container fields.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues
Logs
For example the following configuration includes an incorrect field
container.id
.Before this change, an incomplete configuration is generated, and errors like these ones are logged:
After this change, the cause of the problem is more clear, and it is only logged at the debug level: