Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-22 08:28:52 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 107

docs update (#9104)

Browse source
This commit is contained in:
Sharvil Shah 2022-12-23 01:28:56 +05:30 committed by GitHub
parent 6533c59d1b
commit 082bf024ea
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/Using-Fleet/configuration-files/README.md
View file

@ -884,7 +884,8 @@ spec:
> This feature requires [Orbit, the Fleet agent manager](https://fleetdm.com/announcements/introducing-orbit-your-fleet-agent-manager), along with a custom TUF auto-update server.
The `extensions` key inside of `agent_options` allows you to remotely manage and deploy osquery extensions.
The `extensions` key inside of `agent_options` allows you to remotely manage and deploy osquery extensions. Just like other `agent_options` the `extensions` key can be applied either to a team specific one or the global one.
This is best illustrated with an example. Here is an example of using the `extensions` key:
@ -915,6 +916,11 @@ fleetctl updates add --path /path/to/local/TUF/repo --target /path/to/extensions
After successfully configuring the agent options, and pushing the extension as a target on your TUF server, Orbit will periodically check with the TUF server for updates to these extensions.
If you are using a self-hosted TUF server, you must also manage all of Orbit's versions, including osquery, Fleet Desktop and osquery extensions.
Fleet recommends deploying extensions created with osquery-go or natively with C++, instead of Python. Extensions written in Python requires the user to compile it into a single packaged binary along with all the dependencies.
##### Example Agent options YAML
```yaml