feat: standardize plugin operation invoke API#6
Merged
Conversation
Plugin operation calls are moving to Mission Control's /invoke/ endpoint, while some HTTP-style operations still need the proxy path during the transition.
Default invoke calls now use POST /invoke/:operation and callers can opt into /proxy/:operation with { proxy: true }. The second argument is used as the operation body for body-capable methods or query params for GET and HEAD.
00668b3 to
f68a3d2
Compare
Replace the generic Mission Control client and nested plugins API with a plugin client that creates scoped plugin instances. Plugin instances carry pluginRef and configId, exposing invoke and stream methods that automatically include config_id while preserving invoke-by-default and proxy opt-in behavior.
f68a3d2 to
817bb1a
Compare
This file contains hidden or 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
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.
Plugin operation calls are moving to Mission Control's
/invoke/endpoint, but some HTTP-style operations still need the proxy path during the transition.Update the invoke API to use
POST /invoke/:operationby default and allow callers to opt into/proxy/:operationwith{ proxy: true }.The second argument now represents the operation body for body-capable methods, or query params for
GET/HEAD.