-
Notifications
You must be signed in to change notification settings - Fork 211
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
[Merged by Bors] - Add node merge tool #5685
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #5685 +/- ##
=========================================
- Coverage 79.8% 79.7% -0.1%
=========================================
Files 279 279
Lines 28510 28507 -3
=========================================
- Hits 22760 22739 -21
- Misses 4185 4199 +14
- Partials 1565 1569 +4 ☔ View full report in Codecov by Sentry. |
865b233
to
a666b7e
Compare
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.
i left some cleanups suggestions, but up to you if to fix them
be9c147
to
4386273
Compare
e9efc86
to
87649bb
Compare
bors merge |
## Motivation Adds a new command / tool for merging two nodes into one. Additionally the CI has been updated to include the new tool in a release and build docker images using the right version.
Build failed: |
bors merge |
## Motivation Adds a new command / tool for merging two nodes into one. Additionally the CI has been updated to include the new tool in a release and build docker images using the right version.
Pull request successfully merged into develop. Build succeeded: |
Motivation
Adds a new command / tool for merging two nodes into one. Additionally the CI has been updated to include the new tool in a release and build docker images using the right version.
Description
The CLI tool takes 2 parameters:
--from
which specifies thedata-dir
of the source node which's identities shall be merged to the target node--to
which specifies thedata-dir
of the target node that receives the identities and state of the source node, can be an empty directory (so that a user can setup a new node with all their existing identities merged)The tool only works with nodes that are set up for remote smeshing (i.e. have no
local.key
or supervised post service configuration). It will copy all identities from the source node to the target node while preserving their (file) names and will fail on conflicts (e.g. trying to merge the state of the same identity twice).Test Plan
Tests for the new tool have been added.
TODO