Skip to content

[ti_recordedfuture] - update package-spec to 2.10.0 #7588

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Aug 30, 2023
Merged

[ti_recordedfuture] - update package-spec to 2.10.0 #7588

merged 2 commits into from
Aug 30, 2023

Conversation

taylor-swanson
Copy link
Contributor

@taylor-swanson taylor-swanson commented Aug 29, 2023 •
edited
Loading

What does this PR do?

  • Update package-spec to 2.10.0
  • Ensure event.category is an array
  • Ensure event.type is an array
[git-generate]
go run github.com/andrewkroh/go-examples/ecs-update@latest -ecs-version=8.9.0 -ecs-git-ref=v8.9.0 -format-version=2.10.0 packages/ti_recordedfuture

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.
  • I have verified that Kibana version constraints are current according to guidelines.

Related issues

  • Relates elastic/security-team#5870

@taylor-swanson
[ti_recordedfuture] - update package-spec to 2.10.0
a4ef9ec 
- Update package-spec to 2.10.0
- Ensure event.category is an array
- Ensure event.type is an array

[git-generate]
go run github.com/andrewkroh/go-examples/ecs-update@latest -ecs-version=8.9.0 -ecs-git-ref=v8.9.0 -format-version=2.10.0 -pr=1 packages/ti_recordedfuture
@taylor-swanson taylor-swanson self-assigned this Aug 29, 2023
@elasticmachine
Copy link

elasticmachine commented Aug 29, 2023 •
edited
Loading

💚 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 preview

Expand to view the summary

Build stats

  • Start Time: 2023-08-29T13:11:06.485+0000

  • Duration: 17 min 43 sec

Test stats 🧪

Test Results
Failed 0
Passed 11
Skipped 0
Total 11

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@elasticmachine
Copy link

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 100.0% (1/1) 💚
Files 100.0% (2/2) 💚
Classes 100.0% (2/2) 💚
Methods 100.0% (16/16) 💚 2.222
Lines 97.549% (199/204) 👍 11.364
Conditionals 100.0% (0/0) 💚

@taylor-swanson taylor-swanson marked this pull request as ready for review August 29, 2023 13:32
@taylor-swanson taylor-swanson requested a review from a team as a code owner August 29, 2023 13:32
@elasticmachine
Copy link

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

@taylor-swanson taylor-swanson merged commit 7504912 into elastic:main Aug 30, 2023
@taylor-swanson taylor-swanson deleted the pkg-spec-ti_recordedfuture branch August 30, 2023 13:30
@elasticmachine
Copy link

Package ti_recordedfuture - 1.15.0 containing this change is available at https://epr.elastic.co/search?package=ti_recordedfuture

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@efd6 efd6 efd6 approved these changes

Assignees

@taylor-swanson taylor-swanson

Labels
enhancement New feature or request Integration:ti_recordedfuture Recorded Future
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@taylor-swanson @elasticmachine @efd6