Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-24 09:28:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 31
fleet/frontend/kolide
History
noahtalerman 8e37b8938c
Implement osquery options page (#11) 
Created 3 new components: <OsqueryOptionsPage /> , <OsqueryOptionsForm />, and <YamlAce />

The <OsqueryOptionsPage /> component is rendered at the new route /admin/osquery. The user navigates to this route by selecting the "Osquery Options" sub-navigation in the admin dropdown menu.

On the Osquery Options page, the user is presented with a ACE editor filled with the current osquery options. The current osquery options are retrieved from the serve when the page component mounts. These current osquery options are stored in the osquery slice of state.

Clicking "UPDATE OPTIONS" will trigger a form submit and hit the v1/kolide/spec/osquery_options endpoint if the yaml is valid. If the yaml is not valid, an error message is presented to the user with details on what the error is and where it occurred. If the yaml is valid, the osquery options will be updated even if the options haven't change.
2020-11-04 18:00:51 -08:00
..
entities Implement osquery options page (#11) 2020-11-04 18:00:51 -08:00
base.js Add ability to prefix Fleet URLs (#2112) 2019-10-16 16:40:45 -07:00
endpoints.js Implement osquery options page (#11) 2020-11-04 18:00:51 -08:00
helpers.js Clean up and comments before merge. 2020-07-21 14:05:46 -07:00
helpers.tests.js Implement pagination of hosts in the web UI 2020-07-21 14:05:46 -07:00
index.js Implement osquery options page (#11) 2020-11-04 18:00:51 -08:00
index.tests.js Refactor API client (#1335) 2017-03-02 17:07:01 -05:00
README.md Add Front-end Documentation (#1373) 2017-03-10 17:13:29 -05:00
request.js Refactor API client (#1335) 2017-03-02 17:07:01 -05:00
status.js Add ability to disable live queries (#2167) 2020-01-13 16:53:04 -08:00
websockets.js Refactor API client (#1335) 2017-03-02 17:07:01 -05:00

README.md

Kolide API Client

The Kolide API Client is used for communicating with the Kolide API. Kolide has a number of entities (hosts, labels, packs, queries, users, etc), all of which have CRUD methods to perform on a specific entity or collection of entities.

Entities are assigned to the API Client in the constructor function. Each entity's methods can be found in the /frontend/kolide/entities directory.

The CRUD methods that are typically implemented in the API client are as follows:

create

  • The create method is used for creating a new entity. The input parameter is typically an object containing the attributes for the new entity.

destroy

  • The destroy method is used for deleting an entity. Then input parameter is typically the entity to be deleted.

load

  • The load method is used for loading a single entity. The input parameter is typically the id of the entity to load.

loadAll

  • The loadAll method is used for loading all of the entities.

update

  • The update method is used to update an entity. The input parameters are typically the entity being updated and an object with the updated attributes.