You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is helpful for us when troubleshooting to know which Kolide installers a user has potentially downloaded.
Requirements:
The download checkup should run only for flares (not for launcher doctor or for the log checkpoint -- see here)
The download checkup should write out a list of all Kolide installers found in the downloads directory; installers will have the filename or filename suffix kolide-launcher.msi on Windows, kolide-launcher.pkg on MacOS, and kolide-launcher.rpm, kolide-launcher.deb, or kolide-launcher.pacman on Linux
If possible, the checkup should include launcher version information for those files, if it's feasible and reasonable to extract that information
Hi @20RitikSingh Is Launcher something you're generally involved with? Note that this part of our code base is covered by our EE License and is not open source.
That said, you're welcome to submit a PR. We will not hold this for you, but our PRs are open.
It is helpful for us when troubleshooting to know which Kolide installers a user has potentially downloaded.
Requirements:
launcher doctor
or for the log checkpoint -- see here)kolide-launcher.msi
on Windows,kolide-launcher.pkg
on MacOS, andkolide-launcher.rpm
,kolide-launcher.deb
, orkolide-launcher.pacman
on LinuxCheckups live here in the codebase.
The text was updated successfully, but these errors were encountered: