Skip to content
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

server, client: send full ClusterObject on new eio endpoint #1170

Merged
merged 2 commits into from
Nov 9, 2023

Conversation

bjia56
Copy link
Collaborator

@bjia56 bjia56 commented Nov 9, 2023

Also changes the checksums computed on the python side to be symmetric to node's signatures (both now use base64 encoding).

@koush koush merged commit 7dec399 into koush:main Nov 9, 2023
@bjia56 bjia56 deleted the connect-object-web branch November 9, 2023 20:40
@@ -163,7 +163,18 @@ export class ScryptedRuntime extends PluginHttp<HttpPluginData> {
res.end();
return;
}
if (!req.query.port) {
if (!req.query.clusterObject) {
Copy link
Owner

@koush koush Nov 9, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

couple things I'm just now noticing:

the acl check above is not necessary, non-admin users should be able to access this API.

the cluster object validity check should be done below when the connection is initiated. return some error json and terminate the connection there.

I think this whole handler guard can then be removed with connectRPCObjectHandler in place.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, sounds good will update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants