-
Notifications
You must be signed in to change notification settings - Fork 444
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
Refactor cisco_ise integration #4653
Conversation
💚 CLA has been signed |
@efd6 Next try. Now with changed author email address. CLA check still failing. What's the problem now? |
@Bernhard-Fluehmann Are you able to jump onto the community slack to work through this? Alternatively, can you post the commit details for the change, output from |
a255797
to
ece4ab8
Compare
@efd6 Now? |
Yay! That is working. Thanks for being patient and persistent. |
/test |
🚀 Benchmarks reportTo see the full report comment with |
🌐 Coverage report
|
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.
I like this, the processing is a lot cleaner. I have some suggestions for improvement.
Please re-run elastic-package test -g
; some of the pipline test expectations are not correctly formatted.
Also, this will need to have a changelog entry in changelog.yml and a version bump in manifest.yml. Since this includes enhancements, it should be bumped to "1.3.0".
- name: tmp | ||
type: flattened |
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.
Please delete this.
- name: log_details_object | ||
type: flattened |
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.
This should not be needed since it is only being used temporarily.
- name: log_details | ||
type: text |
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.
If cisco_ise.log.log_details
is being deleted as it now is, this does not need to be in the fields definitions.
I think though that it would be better to leave it here and change it to a flattened
and rename the current cisco_ise.log.log_details_object
to cisco_ise.log.log_details
in the pipeline sources and this field to cisco_ise.log.log_details_raw
as the temporary string to work from. Then if there are any fields that come up in new versions those fields will become clearly visible in this object since they won't have been deleted in the sub-pipelines.
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
- No kv parsing to root level anymore (user log_details_object flattened field instead - More sophisticated parsing of av-pairs - Enhanced error handling - Bug-fixes
2dade2a
to
7da246c
Compare
@efd6 Recommended changes implemented. Please review |
/test |
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.
The README.md will need to be regenerated to incorporate the new sample_event.json. Please run elastic-package build
.
@efd6 Done |
/test |
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.
Thanks
@efd6 Thanks for your fast response and assistance. |
What does this PR do?
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots