Include VSCode Insiders extensions in vscode_extensions table by arymoraes · Pull Request #8396 · osquery/osquery

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For server, we’re already exposing it for the regular VSCode version. If I’m running osquery on WSL and have VSCode on my Windows, the extensions come from the /home/.../.vscode-server/extensions path, for example.

And I agree version_type may not be the best name, as it could get confused with the extension’s version type. vscode_edition seems better. We could omit it, but I think having it as a single column adds clarity.

So maybe keep exposing server and change the column to vscode_edition?