Cherry-pick #20983 to 7.x: [Filebeat][fortinet] Map x509 ecs fields for fortinet fw fileset#21014
Merged
marc-gr merged 1 commit intoelastic:7.xfrom Sep 9, 2020
Merged
Conversation
Contributor
|
Pinging @elastic/siem (Team:SIEM) |
Contributor
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
|
leehinman
requested changes
Sep 8, 2020
CHANGELOG.next.asciidoc
Outdated
Contributor
There was a problem hiding this comment.
looks like cherry_pick script pulled in an extra Changelog line
…stic#20983) * Map x509 ecs fields for fortinet fw fileset * Remove wrongly mapped field and bump ecs version (cherry picked from commit e11283e)
0afc69d to
a604502
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Cherry-pick of PR #20983 to 7.x branch. Original message:
What does this PR do?
Maps x509 fields for firewall fileset
Why is it important?
To keep modules up to date with ecs 1.6
Checklist
- [ ] My code follows the style guidelines of this project- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration filesCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues