-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide Extension API to OpenSearch #74
Conversation
Signed-off-by: Daniel Widdis <widdis@gmail.com>
Signed-off-by: Daniel Widdis <widdis@gmail.com>
Signed-off-by: Daniel Widdis <widdis@gmail.com>
Signed-off-by: Daniel Widdis <widdis@gmail.com>
On extension orchestrator log:
On extension runner log:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Just a small suggestion regarding missing javadocs
Signed-off-by: Daniel Widdis <widdis@gmail.com>
Signed-off-by: Daniel Widdis <widdis@gmail.com>
Signed-off-by: Daniel Widdis <widdis@gmail.com>
Signed-off-by: Daniel Widdis <widdis@gmail.com>
Signed-off-by: Daniel Widdis <widdis@gmail.com>
…ce setter in ExtensionsRunner for testing purporses Signed-off-by: Joshua Palis <jpalis@amazon.com>
Signed-off-by: Daniel Widdis <widdis@gmail.com>
Fixed testHandleExtensionInitRequest
Signed-off-by: Daniel Widdis <widdis@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @dbwiddis. This is a great start for RestAPIs.
Could you update the DESIGN.md
.
I can do that as part of the follow-on PR to address #69 (based a lot on the comment discussing my plan there) to avoid delaying this PR any further. Any other changes needed before this and the companion PR is merged? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the updates, looks good for my perspective
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @dbwiddis.
Gradle check is failing probably because of the PR pending in OpenSearch.
Indeed as it passes locally when they branch is published to maven local. What will it take to get that companion PR approved? I'd like to continue work on both branches. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One small ask :) Rest LGTM!
* Provide Extension API to OpenSearch Signed-off-by: Daniel Widdis <widdis@gmail.com> * Fix newline, add test Signed-off-by: Daniel Widdis <widdis@gmail.com> * Clarify Valid API format Signed-off-by: Daniel Widdis <widdis@gmail.com> * Store uniqueID of extensions Signed-off-by: Daniel Widdis <widdis@gmail.com> * Fix errors in merge commit Signed-off-by: Daniel Widdis <widdis@gmail.com> * Rename Api to RestApi Signed-off-by: Daniel Widdis <widdis@gmail.com> * Delay sending REST API until after responding to initialization Signed-off-by: Daniel Widdis <widdis@gmail.com> * Move YAML file to classpath Signed-off-by: Daniel Widdis <widdis@gmail.com> * Temporarily disable failing test for debug Signed-off-by: Daniel Widdis <widdis@gmail.com> * fixed testHandleExtensionInitRequest, added protected transport service setter in ExtensionsRunner for testing purporses Signed-off-by: Joshua Palis <jpalis@amazon.com> * Change transport service setter to package privage Signed-off-by: Daniel Widdis <widdis@gmail.com> * Rename RestApi to RestActions or RestPaths Signed-off-by: Daniel Widdis <widdis@gmail.com> Signed-off-by: Daniel Widdis <widdis@gmail.com> Signed-off-by: Joshua Palis <jpalis@amazon.com> Co-authored-by: Joshua Palis <jpalis@amazon.com>
Signed-off-by: Daniel Widdis widdis@gmail.com
Description
Companion PR: opensearch-project/OpenSearch#4100
Extensions will report their APIs to the ExtensionsOrchestrator upon initial registration and potentially later in the Extension's lifecycle. These APIs will be registered and mapped so that when Users submit API requests they can be forwarded to the appropriate extensions.
This PR handles the communication of the REST API from the Extension to OpenSearch. Future PRs will complete the process of registering the REST Handlers and redirecting inbound requests.
Issues Resolved
Fixes #68
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.