-
Notifications
You must be signed in to change notification settings - Fork 73
Issues: elastic/package-spec
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[Change Proposal] Relax validations on required fields
discuss
Issue needs discussion
#843
opened Dec 11, 2024 by
jsoriano
[Change Proposal] Add support for ingest pipelines in transforms
discuss
Issue needs discussion
#833
opened Nov 19, 2024 by
jsoriano
[Change Proposal] Add support for "next steps" links to be referenced in Kibana
discuss
Issue needs discussion
Team:Fleet
Label for the Fleet team
#832
opened Nov 18, 2024 by
criamico
[Change Proposal] Support Torch Issue needs discussion
Team:Integrations
Label for the Integrations team
.pt
ML trained models in integration packages
discuss
#830
opened Nov 13, 2024 by
susan-shu-c
5 tasks
[Change Proposal] Add new property to integration to show if their processing can run on Logstash
discuss
Issue needs discussion
#824
opened Oct 24, 2024 by
jsvd
[Enhancement] Scaling options for each integration/data stream
#842
opened Sep 20, 2024 by
lucabelluccini
[Change Proposal] Support additional asset types in content packages
discuss
Issue needs discussion
Team:Ecosystem
Label for the Packages Ecosystem team
#803
opened Sep 19, 2024 by
kpollich
Entity definition use case
discuss
Issue needs discussion
Team:Ecosystem
Label for the Packages Ecosystem team
#783
opened Aug 8, 2024 by
smith
[Change Proposal] Streamline installation for ML integration packages
discuss
Issue needs discussion
Team:Fleet
Label for the Fleet team
#778
opened Jul 19, 2024 by
jmcarlock
Missing a behavioral definition of routing_rules.yml
documentation
Improvements or additions to documentation
#772
opened Jun 26, 2024 by
andrewkroh
[Change Proposal] Skip validation of required fields on packages importing full ECS mappings
discuss
Issue needs discussion
#771
opened Jun 26, 2024 by
jsoriano
[Change Proposal] Allow to define expected_event_types
discuss
Issue needs discussion
#770
opened Jun 26, 2024 by
jsoriano
[Change Proposal] Add special Label for the Packages Ecosystem team
tls
variable types
Team:Ecosystem
#761
opened Jun 11, 2024 by
kpollich
[Change Proposal] Support packages with many fields
discuss
Issue needs discussion
#758
opened Jun 5, 2024 by
jsoriano
[DX] Add reference documentation for each validation code
documentation
Improvements or additions to documentation
#747
opened May 13, 2024 by
andrewkroh
[Change Proposal] Define reusable fields to use in the build dependency system
discuss
Issue needs discussion
#746
opened May 7, 2024 by
pzl
[Change Proposal] Add support for required conditional groups of variables
discuss
Issue needs discussion
#744
opened May 3, 2024 by
jsoriano
[Proposal] Consolidate use of ecs.version field
discuss
Issue needs discussion
#737
opened Apr 15, 2024 by
jsoriano
2 tasks
[Change Proposal] Make version optional in package manifests
discuss
Issue needs discussion
#723
opened Mar 1, 2024 by
jsoriano
[Change Proposal] Support Knowledge Base Packages
discuss
Issue needs discussion
Team:Ecosystem
Label for the Packages Ecosystem team
#693
opened Jan 18, 2024 by
spong
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.