-
Notifications
You must be signed in to change notification settings - Fork 435
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
Bump github.com/elastic/elastic-package from 0.43.0 to 0.44.0 #2916
Bump github.com/elastic/elastic-package from 0.43.0 to 0.44.0 #2916
Conversation
Bumps [github.com/elastic/elastic-package](https://github.com/elastic/elastic-package) from 0.43.0 to 0.44.0. - [Release notes](https://github.com/elastic/elastic-package/releases) - [Changelog](https://github.com/elastic/elastic-package/blob/main/.goreleaser.yml) - [Commits](elastic/elastic-package@v0.43.0...v0.44.0) --- updated-dependencies: - dependency-name: github.com/elastic/elastic-package dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
/test |
…/github.com/elastic/elastic-package-0.44.0
packages/cyberarkpas/docs/README.md
Outdated
| ecs.version | ECS version this event conforms to. `ecs.version` is a required field and must exist in all events. When querying across multiple indices -- which may conform to slightly different ECS versions -- this field lets integrations adjust to the schema version of the events. | keyword | | ||
| error.message | Error message. | match_only_text | | ||
| event.action | The action captured by the event. This describes the information in the event. It is more specific than `event.category`. Examples are `group-add`, `process-started`, `file-created`. The value is normally defined by the implementer. | keyword | | ||
| event.category | This is one of four ECS Categorization Fields, and indicates the second level in the ECS category hierarchy. `event.category` represents the "big buckets" of ECS categories. For example, filtering on `event.category:process` yields all events relating to process activity. This field is closely related to `event.type`, which is used as a subcategory. This field is an array. This will allow proper categorization of some events that fall in multiple categories. | keyword | | ||
| event.code | Identification code for this event, if one exists. Some event sources use event codes to identify messages unambiguously, regardless of message language or wording adjustments over time. An example of this is the Windows Event ID. | keyword | | ||
| event.dataset | Event dataset | constant_keyword | |
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.
Hm... something may be fishy here: constant_keyword
-> keyword
, not sure if this is what we want to achieve?
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.
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.
I am removing the duplicated ECS field by now in ec7f030, so this goes back to its previous format.
@elastic/security-external-integrations please review this part (https://github.com/elastic/integrations/pull/2916/files#diff-ffb7ef2a530f578dd42fcac9c93d03032982b15c37d5fd142fdc61406f5b9cdeL39).
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.
Adding validation for duplicated fields in elastic/package-spec#309.
It looks like a file conflict bumped up in the meantime. |
…/github.com/elastic/elastic-package-0.44.0
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.
Feel free to ship it and use "god mode" to merge this PR.
…stic-package-0.44.0
Bumps github.com/elastic/elastic-package from 0.43.0 to 0.44.0.
Release notes
Sourced from github.com/elastic/elastic-package's releases.
Commits
4845791
Import aditional indexing settings on external fields (#752)9c95e81
Update add-to-ecosystem-project.yml (#763)88075ee
Re-enable AWS tests (#758)34949ba
Update add-to-ecosystem-project.yml (#761)2cc8d9f
Fix: update PR reviewers (#757)1935bf7
Create add-to-ecosystem-project.yml (#759)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)