-
Notifications
You must be signed in to change notification settings - Fork 183
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
Parameterize resource name to support watching other resources in events plugin #62
Conversation
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.
Should we add a test case that covers a resource type other than the default events
?
@rvmiller89 Yes we probably should. @yuting-liu If you are working on tests for watching events, let's add one for another resource type for example pods |
Sure. I'd go ahead adding one test case for this. |
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.
Should we change this log line to:
Starting collection for #{resource_name}.
sumologic-kubernetes-collection/fluent-plugin-events/lib/fluent/plugin/in_events.rb
Line 74 in 6a9be3e
log.info "Starting events collection" |
I didn't update |
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
@ggarg2906sumo FYI, after this PR is merged you'll be able to watch events for a specific resource type in K8s. We want to make sure to cover that in testing |
* adding back in ad * Add enable_ad variable to resources * Missed enable_ad arg in a couple places * and one more * Don't hard code the variable value because duh * Remove auto_gid * Don't set enable_ad in collectors because it has a default * Format terraform * Add enable_ad to root dir * does this still work? * tf fmt Co-authored-by: Malcolm Jones <17786500+mlclmj@users.noreply.github.com>
Introduce new config param
resource_name
to take in a resource name to watch, defaulted toevents
. Use the same config map to store per-resource RV using key in theresource-version-<resource-name>
format.Minor change: rename
apiVersion
toapi_version
to follow the convention of other config param naming.FYI @rvmiller89 @lei-sumo