[processor/resourcedetection] Fix EKS detector nil panic. #227
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lisguo
approved these changes
Aug 23, 2024
mitali-salvi
approved these changes
Aug 23, 2024
This was referenced Sep 3, 2024
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description: If
newK8sDetectorUtilsencounters an error, it will return a nil util and an error. Currently, the error is never logged and the detector is created. When theDetectfunction is called, the nil util is passed into the function and a nil panic occurs.Changed the constructor function to return the error if the util constructor fails. This is similar to the EC2 detector and ECS detector.
Testing: Updated unit tests.