Modified plugin documentation by clarifying valid plugin ID inputs #422
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Joshua Palis <[email protected]>
Naarcha-AWS
reviewed
Feb 23, 2022
Signed-off-by: Joshua Palis <[email protected]>
CEHENKLE
approved these changes
Feb 25, 2022
|
Thanks @joshpalis for taking care of this! |
Naarcha-AWS
approved these changes
Feb 25, 2022
|
@joshpalis reason to close this PR? |
|
I thought this looked pretty good -yeah - not sure why this was closed. |
|
@stockholmux can you please merge this PR? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per issue opensearch-project/OpenSearch#2041, plugin documentation lacks clarification on what are valid plugin IDs
Signed-off-by: Joshua Palis [email protected]