This fixes fleetd-chrome extension -- it now works when loaded in development mode in Chrome. The problem was that fleetd-chrome extension is setting status=1 when query has warnings. Fleet server drops any detail query results with status=1. So, the fleetd-chrome host was never getting fully initialized on the server. - [X] Manual QA for all new/changed functionality
Welcome to the "source available" section of the Fleet codebase. Please note files and functionality under this directory are covered by the Fleet EE License, and require a valid Fleet subscription for production use. See the full license for details.