-
Notifications
You must be signed in to change notification settings - Fork 91
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
Feature/integrate with cc tools #779
base: main
Are you sure you want to change the base?
Feature/integrate with cc tools #779
Conversation
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
39d2366
to
a064eb0
Compare
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
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 tried to follow but wasn't able to compile the changes for main.go
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 @osamamagdy this is pretty cool! Let's shape it a bit more!
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
92e4665
to
1ec09a9
Compare
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
87db6e1
to
ae668f1
Compare
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
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 have not been able to complete the tutorial yet
@osamamagdy I think you can tell staticcheck to ignore the deprecated use issue and thus make CI passing. You find the documentation here: https://staticcheck.dev/docs/configuration/#ignoring-problems |
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
…osamamagdy/fabric-private-chaincode into feature/integrate-with-cc-tools
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
f9e9d15
to
ae77fce
Compare
Signed-off-by: Osama Magdy <59124937+osamamagdy@users.noreply.github.com>
9eab2e5
to
9c485b8
Compare
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
Signed-off-by: osamamagdy <osamamagdy174@gmail.com>
``` | ||
|
||
**Note:** If you're inside the dev environment, you don't need the `sudo` permissions and don't need to `chown` the directory. | ||
The chaincode code structure is different than normal chaincode as it's using the cc-tools framework. |
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 think you need to add an enter here ... I don't think that last sentence is part of the note, correct?
In `$FPC_PATH/samples/chaincode/cc-tools-demo` directory, to build the chaincode and package it as docker image, execute: | ||
|
||
```bash | ||
make |
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.
So I would add a note here that for those that have arm-based computers they should use the method recommended in the main readme for building both the cc-tools-demo chaincode as well as ercc
Open a new terminal and connect to the `fpc-development-go-support` container by running | ||
|
||
```bash | ||
docker exec -it fpc-development-go-support /bin/bash |
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.
are you sure about the name of the environment? I had to change fpc-development-go-support to fpc-development-main .... I am guessing you are using a branch and maybe that is why the difference?
What this PR does / why we need it:
This PR adds a tutorial on how to integrate with cc-tools project, specially using the cc-tools-demo project
Which issue(s) this PR fixes:
Fixes the LFX mentorship project Hyperledger Fabric CC-Tools Support for Fabric Private Chaincode