Add Resolve API #7603
Add Resolve API #7603
Conversation
Signed-off-by: Archer <[email protected]>
Naarcha-AWS
added
API
3 - Tech review
Naarcha-AWS
requested review from
hdhalter,
kolchfa-aws,
vagimeli,
AMoo-Miki,
natebower,
dlvenable,
stephen-crawford and
epugh
as code owners
|
@gbbafna: Can you take a look at this one? |
|
Want to try and author a working test for this in https://github.com/opensearch-project/opensearch-api-specification/tree/main/tests/indices similar to https://github.com/opensearch-project/opensearch-api-specification/blob/main/tests/indices/flush.yaml for example? If you need a data stream, copy from https://github.com/opensearch-project/opensearch-api-specification/blob/main/tests/indices/data_stream.yaml. |
I'll give it a try. |
Signed-off-by: Naarcha-AWS <[email protected]>
|
|
||
| ## Path and HTTP methods | ||
|
|
||
| The Resolve Index API supports the following API method: |
There was a problem hiding this comment.
Do we need this line? We don't have an intro sentence in the template.
| ## Permissions | ||
|
|
||
| When OpenSearch Security is enabled, you must have the `view_index_metadata` or `manage` index permissions for the target data stream, index, or index alias. <!-----FOLLOW UP, Is there a distinction between index permissions and index privileges?> | ||
|
|
There was a problem hiding this comment.
Should we link to the permissions page?
Co-authored-by: Heather Halter <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]>
Closes #2114
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.