Repository navigation
fortinet_fortigate: fix handling of events with from fields - #3901
Merged
Merged
Conversation
Previously, the rename would attempt to redo work already done by the append, causing a pipeline failure. So remove it.
efd6
force-pushed
the
3897-fortinet_fortigate
branch
from
July 29, 2022 12:39
1e57e90 to
380ac87
Compare
efd6
marked this pull request as ready for review
July 29, 2022 12:43
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
🌐 Coverage report
|
taylor-swanson
approved these changes
Jul 29, 2022
taylor-swanson
left a comment
Contributor
There was a problem hiding this comment.
LGTM
I originally made the changes for the append/email, but that rename appears to be an oversight on my part. It should've been removed, which is being done here.
Since fortinet has been split into separate packages, I take it we are deprecating the fortinet package and only maintaining this one from now on?
Contributor
Author
That is my understanding. |
orestisfl
pushed a commit
to orestisfl/integrations
that referenced
this pull request
May 15, 2026
…3901) Previously, the rename would attempt to redo work already done by the append, causing a pipeline failure. So remove it.
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
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.
Previously, the rename would attempt to redo work already done by the
append, causing a pipeline failure. So remove it.
What does this PR do?
This fixes handling of SIP events by removing a redundant rename processor.
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots