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
CORE-20426 Persist the local hosted identities #6123
CORE-20426 Persist the local hosted identities #6123
Conversation
Jenkins build for PR 6123 build 9 Build Successful: |
tools/plugins/upgrade/src/main/kotlin/net/corda/cli/plugins/upgrade/MigrateHostedIdentities.kt
Show resolved
Hide resolved
tools/plugins/upgrade/src/main/kotlin/net/corda/cli/plugins/upgrade/MigrateHostedIdentities.kt
Outdated
Show resolved
Hide resolved
@@ -103,4 +123,162 @@ class MigrateHostedIdentities : Runnable { | |||
UpgradePluginWrapper.logger.error("Failed to close consumer from group '$consumerGroup'.", ex) | |||
} | |||
} | |||
|
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.
Just a heads up in case you weren't aware, the functional part of plugins is moving to a libs/corda-sdk
directory in 5.3 so you wont be able to merge this as is. There's nothing you can do about that here because that component doesn't exist in 5.2.
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.
Thanks. We will need to remember this when the merge bot does a forward merge from release/os/5.2 into release/os/5.3. cc: @YashNabar (we will need to the same for CORE-20478 #6120).
Quality Gate passedIssues Measures |
Change CLI tool to write an SQL to persist the locally hosted identities. This will be used during the 5.2.0 to 5.2.1 platform upgrade process.
Testing
To build, build the CLI plugin and copy the jar into corda-cli-plugin-host:
Then you can run it using:
It will produce SQL which looks like:
To the file
migrate_member_data.sql
. This can be run by adding `SET schema 'config'; before the SQL.