Lab 8 Final Step
At the end of Lab 8 I am prompted to upgrade the chaincode to a version that utilizes the contract API.
If you were initializing a chainode that implements the Fabric contract API (instead of the Fabric
Chaincode Shim API), then you’d need to specify the name of the initialization function to be
called in the chanincode. For example:
peer chaincode invoke -o orderer.example.com:7050 --tls --cafile
$ORDERER_TLS_CA -C allarewelcome -n mychaincode --peerAddresses
$CORE_PEER_ADDRESS --tlsRootCertFiles $CORE_PEER_TLS_ROOTCERT_FILE -c
'{"function":"initLedger","args":["key0", "value0"]}' --isInit
--waitForEvent
We leave as an exercise to the reader to upgrade the sacc chaincode one more time, this time specifying that it must be initialized as described above.
Since there is no chaincode provided or reference that utilizes the contract api I am at a loss as to how to complete this lab. This seems like something that is more focused on fabric developer activities rather than fabric administration.
Is there an expectation for the exam that chaincode will have to be modified? Or should it simply be provided by a developer?
Comments
-
I was able to resolve this by modifying sacc.go and re-deploying:
1. Add import"github.com/hyperledger/fabric-contract-api-go/contractapi"
2. Make SimpleAsset extend/implement contractapi.Contract
3. Make get/set methods public and methods of SimpleAsset
4. Acceptcontractapi.TransactionContextInterface
as first argument to Get/Set
5. Replace calls to stub withctx.GetStub()
6. Delete extraneous code/* * Copyright IBM Corp All Rights Reserved * * SPDX-License-Identifier: Apache-2.0 */ package main import ( "fmt" "github.com/hyperledger/fabric-contract-api-go/contractapi" ) // SimpleAsset implements a simple chaincode to manage an asset type SimpleAsset struct { contractapi.Contract } // Set stores the asset (both key and value) on the ledger. If the key exists, // it will override the value with the new one func (sc *SimpleAsset) Set(ctx contractapi.TransactionContextInterface, args []string) (string, error) { if len(args) != 2 { return "", fmt.Errorf("Incorrect arguments. Expecting a key and a value") } err := ctx.GetStub().PutState(args[0], []byte(args[1])) if err != nil { return "", fmt.Errorf("Failed to set asset: %s", args[0]) } return args[1], nil } // Get returns the value of the specified asset key func (sc *SimpleAsset) Get(ctx contractapi.TransactionContextInterface, args []string) (string, error) { if len(args) != 1 { return "", fmt.Errorf("Incorrect arguments. Expecting a key") } value, err := ctx.GetStub().GetState(args[0]) if err != nil { return "", fmt.Errorf("Failed to get asset: %s with error: %s", args[0], err) } if value == nil { return "", fmt.Errorf("Asset not found: %s", args[0]) } return string(value), nil } // main function starts up the chaincode in the container during instantiate func main() { simpleAsset := new(SimpleAsset) cc, err := contractapi.NewChaincode(simpleAsset) if err != nil { panic(err.Error()) } if err := cc.Start(); err != nil { panic(err.Error()) } }
Due to the nature of the peer CLI and the json ctor argument, invoking was a bit difficult, but I finally accomplished that with the following:
peer chaincode invoke -C allarewelcome -c '{"function":"set","args":["[\"key1\", \"value1\"]"]}' -n sacc --tls --cafile $ORDERER_TLS_CA
0 -
@brentbrownfield, Great job, this information will help other learners. Bobbi
0
Categories
- 8.8K All Categories
- 13 LFX Mentorship
- 66 LFX Mentorship: Linux Kernel
- 355 Linux Foundation Boot Camps
- 227 Cloud Engineer Boot Camp
- 67 Advanced Cloud Engineer Boot Camp
- 23 DevOps Engineer Boot Camp
- 5 Cloud Native Developer Boot Camp
- 732 Training Courses
- 14 LFC110 Class Forum
- 16 LFD102 Class Forum
- 96 LFD103 Class Forum
- 2 LFD121 Class Forum
- 55 LFD201 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 14 LFD254 Class Forum
- 422 LFD259 Class Forum
- 78 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 15 LFS200 Class Forum
- 684 LFS201 Class Forum
- LFS201-JP クラス フォーラム
- 271 LFS211 Class Forum
- 50 LFS216 Class Forum
- 23 LFS241 Class Forum
- 26 LFS242 Class Forum
- 18 LFS243 Class Forum
- 4 LFS244 Class Forum
- 7 LFS250 Class Forum
- LFS250-JP クラス フォーラム
- 105 LFS253 Class Forum
- 753 LFS258 Class Forum
- 7 LFS258-JP クラス フォーラム
- 48 LFS260 Class Forum
- 75 LFS261 Class Forum
- 6 LFS262 Class Forum
- 76 LFS263 Class Forum
- 14 LFS264 Class Forum
- 10 LFS266 Class Forum
- 8 LFS267 Class Forum
- 8 LFS268 Class Forum
- 5 LFS269 Class Forum
- 173 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 184 LFW211 Class Forum
- 100 LFW212 Class Forum
- 876 Hardware
- 205 Drivers
- 74 I/O Devices
- 43 Monitors
- 115 Multimedia
- 204 Networking
- 98 Printers & Scanners
- 82 Storage
- 716 Linux Distributions
- 78 Debian
- 64 Fedora
- 12 Linux Mint
- 13 Mageia
- 22 openSUSE
- 125 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 344 Ubuntu
- 445 Linux System Administration
- 33 Cloud Computing
- 63 Command Line/Scripting
- Github systems admin projects
- 88 Linux Security
- 73 Network Management
- 105 System Management
- 45 Web Management
- 50 Mobile Computing
- 18 Android
- 19 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 499 Off Topic
- 119 Introductions
- 193 Small Talk
- 19 Study Material
- 743 Programming and Development
- 237 Kernel Development
- 472 Software Development
- 899 Software
- 245 Applications
- 178 Command Line
- 2 Compiling/Installing
- 72 Games
- 313 Installation
- 19 All In Program
- 19 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)