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>
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
|
/test |
…/github.com/elastic/elastic-package-0.44.0
| | 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.
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.
There was a problem hiding this comment.
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.
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
mtojek
left a comment
There was a problem hiding this comment.
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
4845791Import aditional indexing settings on external fields (#752)9c95e81Update add-to-ecosystem-project.yml (#763)88075eeRe-enable AWS tests (#758)34949baUpdate add-to-ecosystem-project.yml (#761)2cc8d9fFix: update PR reviewers (#757)1935bf7Create 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)