[FEATURE] Document custom folders

[dblock]

Is your feature request related to a problem?

Document changes in opensearch-project/OpenSearch#848

[JeffHuss]

Taking a look at this.

[JeffHuss]

Seeking feedback on where this would live and how it should be covered. Based on my understanding of the related PR (from the core product) this sounds like guidance for plugin developers rather than OpenSearch users. Bearing that in mind I'm not quite sure where this would go.

[JeffHuss]

In the original issue (opensearch-project/OpenSearch#686) the developer stated that they would work on documentation. In addition to pinging dblock I've also pinged the developer to see what I can learn.

[JeffHuss]

@dblock

[dblock]

@VachaShah see @JeffH-AWS's questions above

[VachaShah]

I think the documentation was added in this commit opensearch-project/opensearch-plugins@d0c019c, the file has changed over time.

I think this would go in a place where we have user documentation for plugins in general - https://opensearch.org/docs/latest/opensearch/install/plugins/. This looks to be a nice place to add documentation for building custom plugins or modify the plugin-descriptor file to add custom folder name and then install/remove using the custom folder name.

[JeffHuss]

@VachaShah can you please link me to the design doc for this? How does an OpenSearch user interact with this setting?

[JeffHuss]

Putting this ticket on the backlog again pending follow-up from someone familiar with the functionality.

[JeffHuss]

Reached out to Vacha again.

[JeffHuss]

I still have not gotten any engagement from Vacha.

Based on re-reviewing the content in the linked commit, this does not seem to belong in the OpenSearch user documentation. These steps seem to be pretty clearly aimed at developers who are customizing or altogether building plugins. The references to changes include Java classes which are not relevant to the operation or use of OpenSearch.

If I'm misunderstanding something please feel free to raise a new issue. At a bare minimum, the issue should include:

• A description of the feature - what does it do?
• Relevancy - why would someone use it?
• Who is the target audience?
• Usage details - how would someone use it?
• Notes including detailed steps on how to enable the feature and verify that it is working as expected