In docs, link to reference for managing osquery extensions (#9099)

- Update "Manage extensions" from 🔜 to  
- Add a "Osquery extensions" section to Using Fleet > Orbit doc page
- Link to reference page in docs
This commit is contained in:
Noah Talerman 2022-12-22 12:32:06 -05:00 committed by GitHub
parent 72aaf14a3b
commit 6533c59d1b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -67,7 +67,7 @@ Now run that installer (double click, on a Mac) to enroll your own computer as a
| Package tooling for Linux `.deb` | ✅ |
| Package tooling for Linux `.rpm` | ✅ |
| Package tooling for Windows `.msi` | ✅ |
| Manage/update osquery extensions | 🔜 |
| Manage/update osquery extensions | |
| Manage cgroups for Linux performance | 🔜 |
## Usage
@ -124,6 +124,12 @@ For example, the following would be a typical drop-in usage of Orbit:
orbit -- --flagfile=flags.txt
```
### Osquery extensions
Orbit can be used to remotely deploy and manage osquery extensions. This saves the time and energy required to maintain extensions using a separate tool like Munki or an MDM solution.
[Learn how](https://fleetdm.com/docs/using-fleet/configuration-files#code-extensions-code-option)
## Packaging
Orbit, like standalone osquery, is typically deployed via OS-specific packages. Tooling is provided with this repository to generate installation packages.