mirror of
https://github.com/elastic/kibana.git
synced 2025-06-27 10:40:07 -04:00
f26d5e622f
## Summary Addresses https://github.com/elastic/kibana/issues/204227 Instead of having to explicitly disable other solutions' plugins in the `serverless.(es|o11y|security|chat).yml` files, this PR proposes an approach to filter them out directly in the plugin discovery mechanism. The PR had to remove: * a bunch of project-specific configurations that are no longer defined in each project. * some global serverless configurations that refer project-specific settings. Risks: * Serverless deployments overriding configs that are no longer known. * Serverless project type A relying on plugin from project type B in some way (side effect?). Mitigation: * Since this is a configuration, we can simply override it (`plugins.allowlistPluginGroups`) if something is broken. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| kibana.yml | ||
| node.options | ||
| README.md | ||
| serverless.chat.yml | ||
| serverless.es.yml | ||
| serverless.oblt.yml | ||
| serverless.security.complete.yml | ||
| serverless.security.essentials.yml | ||
| serverless.security.search_ai_lake.yml | ||
| serverless.security.yml | ||
| serverless.yml | ||
as work on serverless picks up we will add config values to these files that
define how Kibana will run in "serverless" modes. To start Kibana locally with
this configuration, pass --serverless={mode} or run yarn serverless-{mode}
valid modes are currently: es, oblt, security and chat
configuration is applied in the following order, later values override
- serverless.yml (serverless configs go first)
- serverless.{mode}.yml (serverless configs go first)
- base config, in this preference order:
- my-config.yml(s) (set by --config)
- env-config.yml (described by
env.KBN_CONFIG_PATHS) - kibana.yml (default @
env.KBN_PATH_CONF/kibana.yml)
- kibana.dev.yml
- serverless.dev.yml
- serverless.{mode}.dev.yml