-
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
[Security Solution] Filter Default policy details #76112
Conversation
Pinging @elastic/endpoint-management (Team:Endpoint Management) |
Pinging @elastic/endpoint-app-team (Feature:Endpoint) |
x-pack/plugins/security_solution/server/endpoint/routes/policy/service.ts
Outdated
Show resolved
Hide resolved
@elasticmachine merge upstream |
💚 Build SucceededBuild metrics
History
To update your PR or re-run it, just comment with: |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Hi @kevinlog We have validated this ticket on "7.9.2 Snapshot" Elastic Staging Cloud Environment and observed that we are not able to fail the configuration status on endpoint to validate the ticket . Build Details: So could you please share the steps on how to fail the configuration on the endpoint under Administration of security app. thanks !! |
Summary
Fixes a bug, where, if endpoint policy fails to apply, and rolls back to initial policy, then the policy details response differs from the Administration tab (showing success of the rollback, not failure of the attempted policy).
This change filters out the initial policy.
Bug: (we expect statuses to match)
After fix:
Terminal recording of policy call from
master
, then same call from this branch. We want to seestatus: failure
Checklist
Delete any items that are not applicable to this PR.