-
Notifications
You must be signed in to change notification settings - Fork 281
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
docs(examples): migrate supply chain app to ethereum connector #3272
Comments
Could you please assign this issue to me? |
@murluki Yup, you got it! If you need any help, please feel free to reach out to me on the daily pair programming sessions that are open to everyone: https://wiki.hyperledger.org/display/cactus/Daily+Pair+Programming+Calls |
@murluki Just checking in to make sure you are able to progress with this one. How is it going? |
I’ll upload the solution this weekend, but yes, if you don’t mind, could I jump on the call because I do have some questions? |
@murluki Thank you for the update, very much appreciated! You are more than welcome to join the pair programming calls! The next one is coming up on Monday 10:00 AM Pacific Time! |
@murluki Are you still working on this? |
Yes, sorry for making you wait. Finishing. |
@murluki No worries, just keep me in the loop if I can help with any of it! |
Added the change and just checking where else it is used and running the tests/build, thank you! |
@murluki If you share a link to the branch where you are working on, I could help speed things up a bit. :-) |
WORK IN PROGRESS Fixes hyperledger#3272 Signed-off-by: Peter Somogyvari <[email protected]>
1. We are in the process of decomissioning the Quorum connector and this is a pre-requisite to that end. Fixes hyperledger#3272 Signed-off-by: Peter Somogyvari <[email protected]>
1. We are in the process of decomissioning the Quorum connector and this is a pre-requisite to that end. Depends on hyperledger#3379 > test(test-tooling): fix BesuTestLedger start cfg: publish all ports) Fixes hyperledger#3272 Signed-off-by: Peter Somogyvari <[email protected]>
@murluki Sorry, I have to take this one over to make sure it gets done soon. |
1. We are in the process of decomissioning the Quorum connector and this is a pre-requisite to that end. Depends on hyperledger#3379 > test(test-tooling): fix BesuTestLedger start cfg: publish all ports) Fixes hyperledger#3272 Signed-off-by: Peter Somogyvari <[email protected]>
1. We are in the process of decomissioning the Quorum connector and this is a pre-requisite to that end. Depends on hyperledger#3379 > test(test-tooling): fix BesuTestLedger start cfg: publish all ports) Fixes hyperledger#3272 Signed-off-by: Peter Somogyvari <[email protected]>
1. We are in the process of decomissioning the Quorum connector and this is a pre-requisite to that end. Depends on hyperledger#3379 > test(test-tooling): fix BesuTestLedger start cfg: publish all ports) Fixes hyperledger#3272 Signed-off-by: Peter Somogyvari <[email protected]>
Description
There are plans to maybe remove the quorum connector in the future, but for that, we need to first make sure that the example supply chain app still works.
This means migrating the supply chain app from using quorum for storing one of the data entities to another connector such as the ethereum connector (but it could be another one if we figure out along the way as such)
A couple of relevant locations in the code of the supply chain example to speed up context gathering for this task:
A branch that has the changes to remove the quorum connector and it's test utilities (AIO ledgers and such) from the project have already been pushed, but that branch has the build broken at the moment due to the supply chain app's dependency on the quorum connector.
The main goal of this issue is to eliminate that dependency so that the build can start passing on the above referenced branch:
https://github.com/petermetz/cacti/tree/refactor-connector-quorum-removal
Acceptance Criteria
refactor-connector-quorum-removal
has the build passing after having been rebased onto the branch that will be created for fixing this issue.The text was updated successfully, but these errors were encountered: