[eset_protect, lumos, sophos_central] Add Agentless Deployment#19353
Conversation
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
This comment has been minimized.
This comment has been minimized.
TL;DRBuildkite failed in Remediation
Investigation detailsRoot CauseThe failure is from the package lint step enforcing up-to-date README generation, not from runtime/test logic. The log shows a Relevant package field definitions that align with the generated additions include:
And generated docs currently containing those fields (example section):
Evidence
Verification
Follow-upIf this reappears after regeneration, check for uncommitted generated-doc changes in the package and ensure no subsequent field edits were made after the build step. Note 🔒 Integrity filter blocked 2 itemsThe following items were blocked because they don't meet the GitHub integrity level.
To allow these resources, lower tools:
github:
min-integrity: approved # merged | approved | unapproved | noneWhat is this? | From workflow: PR Buildkite Detective Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. |
|
✅ All changelog entries have the correct PR link. |
💚 Build Succeeded
History
|
|
Package eset_protect - 2.4.0 containing this change is available at https://epr.elastic.co/package/eset_protect/2.4.0/ |
|
Package lumos - 1.7.0 containing this change is available at https://epr.elastic.co/package/lumos/1.7.0/ |
|
Package sophos_central - 1.22.0 containing this change is available at https://epr.elastic.co/package/sophos_central/1.22.0/ |
Proposed commit message
Checklist
changelog.ymlfile.How to test this PR locally
Related issues