OpenSearch: How Can We Determine if a Plugin Should Be in the Distribution?

plugin-distro.md

• Pros and cons of being in the distribution, in general.

  • Pros
    • No installation needed by the user. Just enable and go...
    • Certified and approved by the OpenSearch organization
  • Cons
    • Must abide by the rules of OpenSearch including CICD process, security requirements
    • Not every use case may require the plugin

• Pros and cons of NOT being in the distribution

  • Pros
    • Does not bloat the distribution itself.
    • End users can pick and choose what plugins they want
  • Cons
    • No stamp from the OpenSearch project.

• Deciding whether we want a plugin in the distribution, by opening an issue in the plugin repo and first having maintainers of the plugin argue pros/cons of being in the distribution.

  • Probably building a template for this with questions like:
    • What is the use case for the plugin?
    • Other Benefits?

Deciding which version of the distribution to target and when.

Requirements during the plugin development, e.g. gradle build, CI/CD, bcw tests, integ and performance tests. How to onboard into automation, such as version increments. How to onboard into the release manifest in opensearch-build. What is required in terms of security review