-
Notifications
You must be signed in to change notification settings - Fork 32
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
Vulnerability Detection E2E tests: Outdated configuration #5126
Labels
Comments
Rebits
changed the title
Vulnerability Detection E2E tests: Outdated configuration and index name
Vulnerability Detection E2E tests: Outdated configuration
Mar 20, 2024
Currently, using the test's configuration produced the following errors in the environment:
<indexer>
<enabled>yes</enabled>
<hosts>
<host>https://INDEXER-IP:9200</host>
</hosts>
<ssl>
<certificate_authorities>
<ca>/etc/pki/filebeat/root-ca.pem</ca>
</certificate_authorities>
</ssl>
<certificate>/etc/pki/filebeat/node-2.pem</certificate>
<key>/etc/pki/filebeat/node-2-key.pem</key>
</indexer> |
Changed test configuration to: <indexer>
<enabled>yes</enabled>
<hosts>
<host>https://INDEXER-API:9200</host>
</hosts>
<ssl>
<certificate_authorities>
<ca>/etc/pki/filebeat/root-ca.pem</ca>
</certificate_authorities>
<certificate>/etc/pki/filebeat/node-2.pem</certificate>
<key>/etc/pki/filebeat/node-2-key.pem</key>
</ssl>
</indexer> Now, indexer connector is working as expected
Updates the regex for waiting until the end of the vulnerability content process to:
|
LGTM |
This was referenced Apr 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The latest update in version 4.8.0 - Beta 4 introduces significant modifications to the vulnerability detection module's configuration and behavior. As a result, these alterations have caused the E2E Vulnerability Detection test to fail consistently.
Investigation is imperative to identify and implement the necessary adjustments to the tests
The text was updated successfully, but these errors were encountered: