Skip to content

[crowdstrike] add date parsing for BiosReleaseDate field #2867

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

Merged
merged 2 commits into from
Mar 23, 2022

Conversation

leehinman
Copy link
Contributor

What does this PR do?

  • Adds date parsing for the BiosReleaseDate field

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.

Author's Checklist

  • Checked to make sure other date fields were being parsed

How to test this PR locally

elastic-package clean
elastic-package check
elastic-package stack up -d
eval "$(elastic-package stack shellinit)"
elastic-package test

@leehinman leehinman requested a review from a team as a code owner March 22, 2022 18:45
@leehinman leehinman added bug Something isn't working, use only for issues Team:Security-External Integrations labels Mar 22, 2022
@elasticmachine
Copy link

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

@leehinman leehinman force-pushed the 1863_sdh_crowdstrike_date branch from 9779ed0 to 74a784a Compare March 22, 2022 18:46
@elasticmachine
Copy link

elasticmachine commented Mar 22, 2022

💚 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: 2022-03-23T13:23:54.406+0000

  • Duration: 17 min 35 sec

Test stats 🧪

Test Results
Failed 0
Passed 13
Skipped 0
Total 13

🤖 GitHub comments

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

  • /test : Re-trigger the build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working, use only for issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants