mirror of https://github.com/elastic/kibana.git synced 2025-06-27 18:51:07 -04:00

History

Mykola Harmash d0a0a1f9e6 [Infra IU] Disable Metrics Explorer for serverless (#167022 ) Closes #163282 ## Summary This PR: * Adds a `featureFlags.metricsExplorerEnabled` property to the Infra plugin config to enable and disable Metrics Explorer depending on the offering type * Prevents `MetricsExplorerViewsService` initialization for serveless based on the feature flag * Prevents creating Metrics Explorer frontend routes when in serverless * Prevents registration of the MetricsExplorerViews saved object when in serverless * Prevents initialization of the `metrics_explorer_views` API routes when in serverless Trying to access Metrics Explorer in serverless <img width="1829" alt="CleanShot 2023-09-22 at 12 59 35@2x" src="`2b039925`-0f0b-4c07-be29-bbe910de7a34"> Trying to access views API <img width="1829" alt="CleanShot 2023-09-22 at 13 00 00@2x" src="`15269ec2`-becd-4ee3-9b5e-d916df28a7b8"> `infra/metrics_explorer` API still works as per ticket requirements <img width="1829" alt="CleanShot 2023-09-22 at 13 00 06@2x" src="`fb23f912`-c6fd-46c8-9084-c17c51e5b064"> ## How to test * Checkout locally * Enable Infra in `serverless.oblt.yml`: `xpack.infra.enabled: true` * Run Kibana in serverless mode * Try accessing `/app/metrics/explorer` route and make sure it's not available * Make sure other Infra routes (`/app/metrics/inventory` and `/app/metrics/hosts`) still load as expected * In Kibana dev console make sure you get 404 for `GET kbn:/api/infra/metrics_explorer_views` * Also check that you don't see `metrics-explorer-view` saved object in the response for `GET kbn:/api/kibana/management/saved_objects/_allowed_types` * Run Kibana in non-serverless mode and make sure Metrics Explorer is accessible and works as usual --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>		2023-09-29 11:27:19 +02:00
..
plugins	[HTTP] Add build number to headers so that we can identify UIs (#163577 )	2023-08-16 16:05:57 +02:00
services	Elastic License 2.0 (#90099 )	2021-02-03 18:12:39 -08:00
test_suites	[Infra IU] Disable Metrics Explorer for serverless (#167022 )	2023-09-29 11:27:19 +02:00
config.ts	[Telemetry] Fix OptedOut banner (#151084 )	2023-02-14 13:53:55 +01:00
README.md	[KP] Expose new es client (#73651 )	2020-07-30 19:12:37 +02:00

README.md

Plugin Functional Tests

This folder contains plugin functional tests, i.e. functional tests that should be executed against a Kibana instance with specific test plugins available.

To add a plugin to the instance, just place the plugin folder in the plugins directory.

Add new test suites into the test_suites folder and reference them from the config.js file. These test suites work the same as regular functional test except that they are executed against a Kibana with all plugins (from the plugins directory) installed.

Run the test

To run these tests during development you can use the following commands:

# Start the test server (can continue running)
node scripts/functional_tests_server.js --config test/plugin_functional/config.ts
# Start a test run
node scripts/functional_test_runner.js --config test/plugin_functional/config.ts

Run Kibana with a test plugin

In case you want to start Kibana with one of the test plugins (e.g. for developing the test plugin), you can just run:

yarn start --plugin-path=test/plugin_functional/plugins/<plugin_folder>

If you wish to start Kibana with multiple test plugins, you can run:

yarn start --plugin-path=test/plugin_functional/plugins/<plugin_folder1> --plugin-path=test/plugin_functional/plugins/<plugin_folder2> ...

If you wish to load up specific es archived data for your test, you can do so via the es_archiver script detailed in the Scripts README.md

Another option, which will automatically use any specific settings the test environment may rely on, is to boot up the functional test server pointing to the plugin configuration file.

node scripts/functional_tests_server --config test/plugin_functional/config.ts

Note: you may still need to use the es_archiver script to boot up any required data.