Is your feature request related to a problem?
In the current plugin architecture, plugin depends on opensearchplugin which provides OpenSearch with the information required to run the plugin after the installation. Later, the attributes defined in build.gradle like publishing, bundlePlugin, integTest are fetch from OpenSearch and depends on the same.
Since Extensions will be running independently these tasks can't be fetch from OpenSearch because we will be removing the opensearchplugin.
What solution would you like?
- Create a similar gradle plugin like
opensearchplugin named opensearchextension to fetch the dependencies and add an application plugin in the build.gradle file of the extension to run the main class directly.
- Figure out a way to remove the dependencies from OpenSearch and run the above mentioned tasks independently in the SDK.
What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.
Do you have any additional context?
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem?
In the current plugin architecture, plugin depends on
opensearchpluginwhich provides OpenSearch with the information required to run the plugin after the installation. Later, the attributes defined in build.gradle likepublishing,bundlePlugin,integTestare fetch from OpenSearch and depends on the same.Since Extensions will be running independently these tasks can't be fetch from OpenSearch because we will be removing the
opensearchplugin.What solution would you like?
opensearchpluginnamedopensearchextensionto fetch the dependencies and add anapplicationplugin in the build.gradle file of the extension to run the main class directly.What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.
Do you have any additional context?
Add any other context or screenshots about the feature request here.