History

Sonja Krause-Harder efcf7d1a25 [Fleet] Don't fail on errors in 'update' or 'reupdate' operation in /setup (#97404 ) * Don't fail on, just report, update and reupdate errors. * Show error toast on update and reupdate errors. * Don't return empty error array. * Adjust mock. * Adjust test.		2021-04-19 16:01:10 +02:00
..
common	[Fleet] Don't fail on errors in 'update' or 'reupdate' operation in /setup (#97404 )	2021-04-19 16:01:10 +02:00
dev_docs	[Fleet] Remove support for shared_id during enrollment (#88897 )	2021-01-21 13:42:39 -05:00
public	[Fleet] Don't fail on errors in 'update' or 'reupdate' operation in /setup (#97404 )	2021-04-19 16:01:10 +02:00
server	[Fleet] Don't fail on errors in 'update' or 'reupdate' operation in /setup (#97404 )	2021-04-19 16:01:10 +02:00
CHANGELOG.md
jest.config.js	Elastic License 2.0 (#90099 )	2021-02-03 18:12:39 -08:00
kibana.json	Do not generate an ephemeral encryption key in production. (#81511 )	2021-02-10 11:27:31 +01:00
package.json	[Fleet] Rename ingestManager plugin ID fleet (#83200 )	2020-11-19 08:43:14 -05:00
README.md	[Fleet] Rename ingestManager plugin ID fleet (#83200 )	2020-11-19 08:43:14 -05:00
tsconfig.json	Revert "TS Incremental build exclude test files (#95610 )" (#96223 )	2021-04-05 11:59:26 -07:00

README.md

Fleet

Plugin

The plugin is enabled by default. See the TypeScript type for the the available plugin configuration options
Adding xpack.fleet.enabled=false will disable the plugin including the EPM and Fleet features. It will also remove the PACKAGE_POLICY_API_ROUTES and AGENT_POLICY_API_ROUTES values in common/constants/routes.ts
Adding --xpack.fleet.agents.enabled=false will disable the Fleet API & UI
- code for adding the routes
- Integration tests
Both EPM and Fleet require ingestManager be enabled. They are not standalone features.
For Enterprise license, a custom package registry URL can be used by setting xpack.fleet.registryUrl=http://localhost:8080
- This property is currently only for internal Elastic development and is unsupported

Fleet Requirements

Fleet needs to have Elasticsearch API keys enabled, and also to have TLS enabled on kibana, (if you want to run Kibana without TLS you can provide the following config flag --xpack.fleet.agents.tlsCheckDisabled=false)

Also you need to configure the hosts your agent is going to use to comunication with Elasticsearch and Kibana (Not needed if you use Elastic cloud). You can use the following flags:

--xpack.fleet.agents.elasticsearch.host=http://localhost:9200
--xpack.fleet.agents.kibana.host=http://localhost:5601

Development

Getting started

See the Kibana docs for how to set up your dev environment, run Elasticsearch, and start Kibana

One common development workflow is:

Bootstrap Kibana
```
yarn kbn bootstrap
```

Start Elasticsearch in one shell

yarn es snapshot -E xpack.security.authc.api_key.enabled=true

Start Kibana in another shell

yarn start --xpack.fleet.enabled=true --no-base-path

This plugin follows the common, server, public structure from the Architecture Style Guide . We also follow the pattern of developing feature branches under your personal fork of Kibana.

Note: The plugin was previously named Ingest Manager it's possible that some variables are still named with that old plugin name.

Tests

API integration tests

You need to have docker to run ingest manager api integration tests

In one terminal, run the tests from the Kibana root directory with

FLEET_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:server --config x-pack/test/fleet_api_integration/config.ts

in a second terminal, run the tests from the Kibana root directory with

FLEET_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:runner --config x-pack/test/fleet_api_integration/config.ts

Optionally you can filter which tests you want to run using --grep

FLEET_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:runner --config x-pack/test/fleet_api_integration/config.ts --grep='fleet'