-
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
Fix NewContainerMetadataEnricher to use default config for kubernetes module. #16857
Conversation
Pinging @elastic/integrations-platforms (Team:Platforms) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm.
Note here that this change will be applied on both ResourceMetadataEnricher
and ContainerMetadataEnricher
, right? However, I guess that this is sth that we want. If so we need to update the PR description and add the respective changelog entry.
@ChrsMark Added changelog entry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
… module. (elastic#16857) * Fix code to use default config for resource metadata. * Add changelog entry. (cherry picked from commit 5c38912)
@blakerouse maybe this should be backported to |
… module. (elastic#16857) * Fix code to use default config for resource metadata. * Add changelog entry. (cherry picked from commit 5c38912)
What does this PR do?
Fix
NewContainerMetadataEnricher
to use default values formetadata.Config
.ResourceMetadataEnricher
already used the default config.This also includes a change to use
InitDefaults
so an new call sites do not need to worry about ensuring the default config is always used before unpacking.Why is it important?
So
labels.dedot
andannotations.dedot
default totrue
.Checklist
I have commented my code, particularly in hard-to-understand areasI have made corresponding changes to the documentationI have made corresponding change to the default configuration files(already was supposed to be default)I have added tests that prove my fix is effective or that my feature worksAuthor's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs