mirror of
https://github.com/elastic/kibana.git
synced 2025-04-26 02:37:44 -04:00
ab8a2f7427
* Initial conversion to asciidoc * Update and split migration guide * Convert MIGRATION_EXAMPLES to asciidoc * build with --focus flag * convert migration guide to asciidoc * cleanup migration_examples * fix wrong Heading size * update links in docs * Apply suggestions from code review Co-authored-by: Rudolf Meijering <skaapgif@gmail.com> * Apply suggestions from code review Co-authored-by: Rudolf Meijering <skaapgif@gmail.com> * add tooling section * explain purpose of each lifecycle method * cleanup docs * cleanup p2 * fix wrong link * resturcture core docs * fix wrong link * update missing links * Apply suggestions from code review Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com> * address comments * add a commenta about plugin-helpers preconfigured * improve density of tables * fix lik * remove links to the migration guide * address comments * Apply suggestions from code review Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com> * address @gchaps comments * Apply suggestions from code review Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com> * change format of ES client change list Co-authored-by: Josh Dover <me@joshdover.com> Co-authored-by: Rudolf Meijering <skaapgif@gmail.com> Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com>
24 lines
1.3 KiB
Text
24 lines
1.3 KiB
Text
[[external-plugin-development]]
|
|
== External plugin development
|
|
|
|
[IMPORTANT]
|
|
==============================================
|
|
The {kib} plugin interfaces are in a state of constant development. We cannot provide backwards compatibility for plugins due to the high rate of change. {kib} enforces that the installed plugins match the version of {kib} itself. Plugin developers will have to release a new version of their plugin for each new {kib} release as a result.
|
|
==============================================
|
|
|
|
Most developers who contribute code directly to the {kib} repo are writing code inside plugins, so our <<contributing>> docs are the best place to
|
|
start. However, there are a few differences when developing plugins outside the {kib} repo. These differences are covered here.
|
|
|
|
* <<plugin-tooling>>
|
|
* <<migrating-legacy-plugins>>
|
|
* <<migrating-legacy-plugins-examples>>
|
|
* <<external-plugin-functional-tests>>
|
|
* <<external-plugin-localization>>
|
|
* <<testing-kibana-plugin>>
|
|
|
|
include::plugin-tooling.asciidoc[leveloffset=+1]
|
|
include::migrating-legacy-plugins.asciidoc[leveloffset=+1]
|
|
include::migrating-legacy-plugins-examples.asciidoc[leveloffset=+1]
|
|
include::external-plugin-functional-tests.asciidoc[leveloffset=+1]
|
|
include::external-plugin-localization.asciidoc[leveloffset=+1]
|
|
include::testing-kibana-plugin.asciidoc[leveloffset=+1]
|