-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Node service plugins #5072
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
base: main
Are you sure you want to change the base?
Node service plugins #5072
Conversation
|
|
||
| Default value: `0` | ||
| * `--port <PORT>` — The port on which to run the server | ||
| * `--operator-application-ids <OPERATOR_APPLICATION_IDS>` — Application IDs of operator applications to watch. When specified, a task processor is started alongside the node service |
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.
"operator application" is not quite right because some of these applications may not use an "operator" at all. Let's do a round of brainstorming
ma2bd
left a comment
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.
@bart-linera Thanks for the PR. This looks awesome
Motivation
On a private repository Mathieu started working on an alternative node service with a plugin system for external processes that want to interact with apps and commit operations.
Proposal
Add the plugin system to the node service itself. (The task processor part done by Claude, but reviewed.)
This PR is an extension of #5056
Test Plan
CI
(Claude added a test; to extend that we'd have to write an example app that requests actions from a plugin.)
Release Plan
testnetbranch, thenLinks