Open juliaElastic opened 3 years ago
Pinging @elastic/security-solution (Team: SecuritySolution)
Pinging @elastic/security-onboarding-and-lifecycle-mgt (Team:Onboarding and Lifecycle Mgt)
@juliaElastic the Endpoint integration is initially enabled with a default policy, so this might be the issue.
For clarity, are you saying that if you add antivirus_registration
and popup.message
fields in your initial POST call that they are not present at all? Or are the fields present, but they don't retain the fields that you set?
A before and after of each of the Policy bodies will help. Thanks!
fyi @paul-tavares @parkiino let me know if there is anything in here that stands out.
Describe the bug: User reported here https://discuss.elastic.co/t/fleet-api-vs-fleet-ui/283918 When creating a package_policy Endpoint using API, some fields are not persisted. This is not happening when the package_policy is updated.
Kibana/Elasticsearch Stack version: 8.0.0, probably 7.x too
Server OS version: macOS Big Sur 11.5.2
Browser and Browser OS versions: N/A
Elastic Endpoint version:
Original install method (e.g. download page, yum, from source, etc.): download page
Functional Area (e.g. Endpoint management, timelines, resolver, etc.): Endpoint management
Steps to reproduce:
See example body here:
Current behavior: Some fields are not persisted on creation
Expected behavior: All fields should be persisted on creation
Screenshots (if relevant):
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Any additional context (logs, chat logs, magical formulas, etc.): Errors are coming from this logic: : x-pack/plugins/security_solution/server/fleet_integration/handlers/install_prepackaged_rules.ts:63