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

Update index mapping for CNVM findings #6069

Conversation

uri-weisman
Copy link
Contributor

What does this PR do?

Update CNVM index mapping

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

  • [ ]

How to test this PR locally

Run together with elastic/cloudbeat#912

Related issues

Screenshots

Screenshot 2023-05-03 at 14 29 26

@uri-weisman uri-weisman requested a review from a team as a code owner May 3, 2023 11:58
@uri-weisman uri-weisman changed the base branch from main to backport-cloud_security_posture-1.3 May 3, 2023 12:11
@uri-weisman uri-weisman requested a review from kfirpeled May 3, 2023 12:13
@uri-weisman uri-weisman mentioned this pull request May 3, 2023
4 tasks
@elasticmachine
Copy link

elasticmachine commented May 3, 2023

💚 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-05-04T06:35:28.688+0000

  • Duration: 14 min 4 sec

Test stats 🧪

Test Results
Failed 0
Passed 4
Skipped 0
Total 4

🤖 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

elasticmachine commented May 3, 2023

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 100.0% (0/0) 💚
Files 100.0% (0/0) 💚
Classes 100.0% (0/0) 💚
Methods 25.0% (2/8) 👎 -35.759
Lines 100.0% (0/0) 💚 0.465
Conditionals 100.0% (0/0) 💚

@kfirpeled
Copy link
Contributor

@uri-weisman don't forget to make another pull request into main as well
You can keep that change in the changelog under 1.3.0 for the sake of keeping that list aligned

@uri-weisman uri-weisman merged commit bddadad into elastic:backport-cloud_security_posture-1.3 May 4, 2023
1 check passed
@uri-weisman uri-weisman deleted the backport-cloud_security_posture-1.3 branch May 4, 2023 06:50
@uri-weisman uri-weisman linked an issue May 4, 2023 that may be closed by this pull request
4 tasks
@elasticmachine
Copy link

Package cloud_security_posture - 1.3.0-preview8 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture

@elasticmachine
Copy link

Package cloud_security_posture - 1.3.0-preview9 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture

@elasticmachine
Copy link

Package cloud_security_posture - 1.3.0-preview10 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture

@elasticmachine
Copy link

Package cloud_security_posture - 1.3.0-preview91 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture

@elasticmachine
Copy link

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

@kfirpeled kfirpeled added the Team:Cloud Security Label for the Cloud Security team label Jun 26, 2023
@elasticmachine
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Cloud Security Label for the Cloud Security team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Move non-ECS fields from root level event
3 participants