-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Cloud Posture] - Fixing CSP no fleet agent error #148632
[Cloud Posture] - Fixing CSP no fleet agent error #148632
Conversation
Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security) |
…_cloudbeat' into fleet_agent_index_catch_error_in_cloudbeat
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.
minor changes:
1 - remove changes on our FTR from this PR (done in another)
2 - define schema in module scope
@@ -32,7 +32,7 @@ export default function ({ getPageObjects, getService }: FtrProviderContext) { | |||
const ruleName2 = data[1].rule.name; | |||
|
|||
// Failing: See https://github.com/elastic/kibana/issues/147998 | |||
describe.skip('Findings Page', () => { | |||
describe('Findings Page', () => { |
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.
please remove changes to this file, we're going to do it in a separate PR with a few other FTR changes as well.
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
History
To update your PR or re-run it, just comment with: |
Summary
In the past fleet wouldn't throw an error when the agent index wasn't found, today it throws.
We would like to catch this specific error in our plugin so the plugin behavior will remain the same
For maintainers