Skip to content
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

[fortinet] Make event.original optional in fortinet #1075

Merged
merged 1 commit into from
Jun 3, 2021

Conversation

marc-gr
Copy link
Contributor

@marc-gr marc-gr commented Jun 3, 2021

What does this PR do?

Makes event.original optional

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
    - [] If I'm introducing a new feature, I have modified the Kibana version constraint in my package's manifest.yml file to point to the latest Elastic stack release (e.g. ^7.13.0).

Related issues

Screenshots

@elasticmachine
Copy link

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@marc-gr marc-gr force-pushed the fortinet-eventoriginal branch 2 times, most recently from 5dd8a19 to 707d74d Compare June 3, 2021 12:26
@elasticmachine
Copy link

elasticmachine commented Jun 3, 2021

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: Pull request #1075 updated

  • Start Time: 2021-06-03T12:48:17.087+0000

  • Duration: 30 min 58 sec

  • Commit: 4ca5622

Test stats 🧪

Test Results
Failed 0
Passed 25
Skipped 0
Total 25

Trends 🧪

Image of Build Times

Image of Tests

@marc-gr marc-gr mentioned this pull request Jun 3, 2021
43 tasks
Copy link
Member

@P1llus P1llus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just a quick comment you should check first.

{{#if internal_interfaces.length}}
{{else}}
{{#if external_interfaces.length}}
processors:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is processors meant to be twice here?

{{#if internal_interfaces.length}}
{{else}}
{{#if external_interfaces.length}}
processors:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is processors meant to be twice here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is added only once, in case any of internal_interfaces and external_interfaces are set, otherwise processors can be empty and it was breaking the system tests. This if else if is needed since handlebars lacks an || operator.

@marc-gr marc-gr merged commit bd52635 into elastic:master Jun 3, 2021
@marc-gr marc-gr deleted the fortinet-eventoriginal branch June 3, 2021 14:25
james-elastic pushed a commit to james-elastic/integrations that referenced this pull request Jun 30, 2021
eyalkraft pushed a commit to build-security/integrations that referenced this pull request Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants