dc1d98ba17
* WIP: Re-create separation of integrations app
* Fix breadcrumbs
* Fix add integration button/routing
* Fix integrations test paths
* Fix failing policy tab tests
* Fix type errors
* Fix more type errors
* Fix integrations home page redirect
* Fix circular import
* Fix i18n errors
* Fix FTR paths
* Fix more deep fleet import paths
* Remove unneeded state set
* Fix more type errors
* Fix failing security_solutions tests
* Address redirect back path todo
* Fix page path in FTR
* Fix type error
* 🤞 Fix FTR failures
* Fix package details path in endpoint tests
* Fix test import
* Fix add integration route + breadcrumbs
* Fix missing layout for create package policy page
* Fixup Kibana feature declaration + fix app registry arrays
* Fix Kibana startup error from feature registration
* Fix telemetry schema
* Remove integrations from privilege tests
* Increase Fleet bundle limit by 20kb to fix CI error
* Use correct updated Fleet bundle limit
* Update limits.yml via script
* Address design feedback
* Fix i18n error
* Fix failing security solution tests
* Fix type error
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
|
||
|---|---|---|
| .. | ||
| common | ||
| dev_docs | ||
| public | ||
| server | ||
| CHANGELOG.md | ||
| jest.config.js | ||
| kibana.json | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
Fleet
Plugin
- The plugin is enabled by default. See the TypeScript type for the the available plugin configuration options
- Adding
xpack.fleet.enabled=falsewill disable the plugin including the EPM and Fleet features. It will also remove thePACKAGE_POLICY_API_ROUTESandAGENT_POLICY_API_ROUTESvalues incommon/constants/routes.ts - Adding
--xpack.fleet.agents.enabled=falsewill disable the Fleet API & UI - Both EPM and Fleet require
ingestManagerbe 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.tsOptionally you can filter which tests you want to run using
--grepFLEET_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:runner --config x-pack/test/fleet_api_integration/config.ts --grep='fleet'