lastpass: use explicit JSON serialisation in response transform#19811
Conversation
A Beats regression (elastic/beats#50384) changed response body template values from mapstr.M (whose String method produces JSON) to plain map[string]interface{} (whose String method produces Go map syntax). This breaks the detailed_shared_folder response transform which renders the whole body with value_type: json. Use the toJSON template function to serialise the body explicitly, bypassing the implicit serialisation path. Updates elastic#18754 Updates elastic#19767 Updates elastic#19774
9d236c5 to
b81bf88
Compare
✅ 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. |
|
✅ All changelog entries have the correct PR link. |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
cc @efd6 |
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
|
👀 I have started reviewing the PR |
Vera Review BotFor the current commit state, I did not find any issues. 🤖 AI-Generated Review | Vera Review Bot | 📚 Knowledge base: integration-skills
|
|
Tick the box to add this pull request to the merge queue (same as
|
|
Package lastpass - 1.23.1 containing this change is available at https://epr.elastic.co/package/lastpass/1.23.1/ |
Proposed commit message
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots