Fix cassandra and icmp comments in packetbeat.yml#22584
Fix cassandra and icmp comments in packetbeat.yml#22584andrewkroh merged 4 commits intoelastic:masterfrom yzdann:master
Conversation
|
💚 CLA has been signed |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
|
Hi! We're labeling this issue as |
|
👍 |
andrewkroh
left a comment
There was a problem hiding this comment.
I updated the templates used to generate the config files with your changes.
* Uniform cassandra comment in packetbeat.yml * Fix icmp comment in packetbeat.yml * Uniform SIP comment in packetbeat.yml * Update the config templates Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co> (cherry picked from commit 6cad281)
* Uniform cassandra comment in packetbeat.yml * Fix icmp comment in packetbeat.yml * Uniform SIP comment in packetbeat.yml * Update the config templates Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co> (cherry picked from commit 6cad281) Co-authored-by: Yazdan <22779039+yzdann@users.noreply.github.com>
What does this PR do?
Fix and Uniform comments in packetbeat.yml
Why is it important?
Checklist
I have commented my code, particularly in hard-to-understand areasI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksI have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs