feat: Implement STIM bundle decryption and installation #34
Conversation
- Updated `Worker.handleDeploy` to handle STIM bundles using `ExtractProfileBundle` and `ExtractMinerBundle`. - Used `PeerConnection.SharedSecret` as the password for decryption. - Implemented logic for `BundleProfile`, `BundleMiner`, and `BundleFull`. - Fixed broken files `pkg/node/dispatcher.go` and `pkg/node/peer.go` to ensure compilation and testing. - Updated tests in `pkg/node/worker_test.go` and added coverage for deployment logic.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
This PR implements the logic for handling STIM encrypted deployment bundles in the worker node. It enables the worker to decrypt and install profiles and miners sent via the
MsgDeploymessage, using the peer connection's shared secret as the decryption key. It also includes fixes fordispatcher.goandpeer.gowhich were preventing compilation and testing.PR created automatically by Jules for task 6939092401374393259 started by @Snider