-
Notifications
You must be signed in to change notification settings - Fork 474
[GitHub][Security Advisories] Fix - include advisory_type in state for next interval #14273
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
Conversation
🚀 Benchmarks reportTo see the full report comment with |
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
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.
Fix LGTM, but there are unrelated or unnecessary changes that I think should be reverted. If these are require for other changes, they should be in a separate PR.
packages/github/kibana/dashboard/github-8bfd8310-205c-11ec-8b10-11a4c5e322a0.json
Outdated
Show resolved
Hide resolved
packages/github/data_stream/security_advisories/sample_event.json
Outdated
Show resolved
Hide resolved
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
💚 Build Succeeded
History
|
|
Package github - 2.8.1 containing this change is available at https://epr.elastic.co/package/github/2.8.1/ |
I had the following error.

I realised that after the first interval, the second interval call is missing the
advisory_type
. By adding it to the state, it should fix the issue.