Prep for Release 9.0 #4502
Open
Prep for Release 9.0 #4502
+9,164
−7,577
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shashank-elastic
requested review from
Mikaayenson,
eric-forte-elastic and
terrancedejesus
as code owners
botelastic
bot
added
bbr
Enhancement - GuidelinesThese guidelines serve as a reminder set of considerations when addressing adding a feature to the code. Documentation and Context
Code Standards and Practices
Testing
Additional Checks
|
1 similar comment
Enhancement - GuidelinesThese guidelines serve as a reminder set of considerations when addressing adding a feature to the code. Documentation and Context
Code Standards and Practices
Testing
Additional Checks
|
|
⛔️ Tests failed: |
|
⛔️ Tests failed: |
|
⛔️ Tests failed: |
This reverts commit 6717fa6.
=========================== short test summary info ============================
FAILED tests/test_all_rules.py::TestValidRules::test_rule_type_changes - ValueError: no compatible version for integration apm:None
FAILED tests/test_packages.py::TestPackages::test_package_loader_default_configs - ValueError: no compatible version for integration apm:None
FAILED tests/test_packages.py::TestPackages::test_package_summary - ValueError: no compatible version for integration apm:None
FAILED tests/test_packages.py::TestPackages::test_rule_versioning - ValueError: no compatible version for integration apm:None
But We saw Rule Loader failures on the same like this https://github.com/elastic/detection-rules/actions/runs/13567900791/job/37925126659?pr=4502 , so we have got back to the stage of APM rule loader failures. |
|
This should be carefully considered about implications to our OOTB package and the repo. Couple of things I noticed.
|
|
Thanks @terrancedejesus
|
|
⛔️ Tests failed: |
|
With the latest integrations and schemas, we encountered this error. Suspecting beats changes we reverted back to the older beats version but it still points to apm integration Since its a BB rule, i just removed the rule to see if we hit any other issues with package compatibility. As suspected we dont have a package for windows that is compatible with 9.0.0 The latest manifest still supports only ^8.14.0. Which makes me think how many packages would have this issue ? |
|
All these Integration Packages, which are dependant on rule integrations still do not have 9.0.0 version compatible.
|
|
Dependent on the following things @Mikaayenson |
|
⛔️ Tests failed:
|
5 tasks
|
⛔️ Tests failed:
|
Latest List of Packages not having manifest is reported and here is the list |
|
Hi @shashank-elastic we at SecML updated our packages, see the PR:
Versions after the change are: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request
Issue link(s): As part of Release https://github.com/elastic/ia-trade-team/issues/565
Summary - What I changed
Rule Changes
How To Test
Blockers
- network_traffic
- fim
- auditd_manager
- panw
Checklist
bug,enhancement,schema,maintenance,Rule: New,Rule: Deprecation,Rule: Tuning,Hunt: New, orHunt: Tuningso guidelines can be generatedmeta:rapid-mergelabel if planning to merge within 24 hoursContributor checklist