-
Notifications
You must be signed in to change notification settings - Fork 71
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
Install chaincode from docker image #445
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: roopsai surampudi <roopsai@outlook.in>
Signed-off-by: roopsai surampudi <roopsai@outlook.in>
Signed-off-by: roopsai surampudi <roopsai@outlook.in>
Signed-off-by: roopsai surampudi <roopsai@outlook.in>
Signed-off-by: roopsai surampudi <roopsai@outlook.in>
Signed-off-by: roopsai surampudi <roopsai@outlook.in>
@@ -12,64 +12,69 @@ dockerPullIfMissing() { | |||
chaincodeBuild() { |
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 would recommend to split it into two functions:
chaincodeBuildDirPath
, chaincodeBuildImage
It would simplify the logic chaincode-install-v2 and would mean that we don't need to make if checks inside script
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.
Ok 😊
"<%= chaincode.lang %>" <% -%> | ||
"<%= chaincode.image %>" | ||
"<%= global.fabricRecommendedNodeVersion %>" | ||
<% } -%> |
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.
As I've written below, having two independent functions chaincodeBuildDirPath
, chaincodeBuildImage
would simplify this logic, thanks to it we don't need to have if statements inside functions.
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.
Also, to be considered - maybe it is even possible to do build->package->install if we have directory, and just a single step if we have docker image. The flow might be slightly different
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.
The flow for deploying Chaincode-as-a-Service is build/pull a Docker Image -> Package A Chaincode (only contains connection details) -> Install -> Run the Chaincode-as-a-service Containers.
Reminder for later: Remember about adding snapshots when you'll finish the task. |
Signed-off-by: roopsai surampudi <roopsai@outlook.in>
Signed-off-by: roopsai surampudi <roopsai@outlook.in>
Signed-off-by: roopsai surampudi <roopsai@outlook.in>
Signed-off-by: roopsai surampudi <roopsai@outlook.in>
Signed-off-by: roopsai surampudi <roopsai@outlook.in>
Signed-off-by: roopsai <roopsai@outlook.in>
Signed-off-by: roopsai surampudi <roopsai@outlook.in>
Signed-off-by: roopsai surampudi <roopsai@outlook.in>
No description provided.