-
Notifications
You must be signed in to change notification settings - Fork 15
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
5828.1 Backend provision for uploading and installing plugin #5924
base: 5827-Backend-plugin-table
Are you sure you want to change the base?
5828.1 Backend provision for uploading and installing plugin #5924
Conversation
β¦n-for-uploading-and-installing-plugin
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.
Look good to me.
Feels like there's a bit of refinement to go, will be nice to test it out once the UI is there and sync.
Haven't tested sync at all as I assume that can wait till the next PR to use processors...
#[error("Failed to open manifest file {0}")] | ||
CannotOpenManifestFile(PathBuf, #[source] std::io::Error), | ||
#[error("Failed to parse manifest file {0}")] | ||
CannotManifestFile(PathBuf, #[source] serde_json::Error), |
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.
CannotManifestFile(PathBuf, #[source] serde_json::Error), | |
CannotReadManifestFile(PathBuf, #[source] serde_json::Error), |
|
||
// This endpoint can be use for uploading files before they need to be processed (via graphql endpoint) | ||
|
||
#[post("/upload")] |
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.
#[post("/upload")] | |
#[post("/config_upload")] |
Note sure the best wording but I think upload is a bit too generic...
Fixes #5828
π©π»βπ» What does this PR do?
Limited info is returned currently by uploadedPluginInfo endpoint, the idea is it would be indicator to the user of what will be imported (didn't want to expand too much atm)
π Any notes for the reviewer?
Versioning will be added at some point, similar to report where report id would be code + version), this would be done by bundler
There is still a follow up PRs for
1 - Frontend UI for importing plugins
2 - Binding plugins via processors (so that after sync it's available) and on startup
3 - Versioning
π§ͺ Testing
Go through tests in amc.js, and see how it effects database (with backend_plugin table and amc calulcation).
π Documentation
1.
2.