arsulegai / fabric-debugger Goto Github PK

The ask is to identify the command capability of the VS Code extension. Consider the following:

1. A developer passes a running Hyperledger Fabric network configuration file to the debugger extension we're building.
2. The extension would need to install the smart contract in the runtime instance of one of the peer nodes.
3. Hyperledger Fabric follows lifecycle of the chaincode which has install, approve and commit as the steps.

At the bare minimum, one should be able to install, approve and commit on demand. In other simplified option, a run action triggered by the user should automatically run these commands behind the scene.

Assumption:

• The user has flexibility to configure the chaincode name used for installation.
• The debugger plugin will spit out information such as insufficient permission to run the debugger itself. It is the responsibility of the smart contract developer to pass a valid runtime of Hyperledger Fabric network.

The expectation here is to document, and the relevant links from the VS Code's documentation, including sample codebase. The ask is to create a sample plugin that would print "Hello World".

An individual task list can be created as a research activity for each of the following.

Note:

1. Identify and document any system dependencies. For instance, VS Code plugin while working on Mac vs Windows. The finding could be in terms of the default configurations, the system dependencies.
2. Research how to run the codebase, along with opening of port. Imagine running chaincode as a service, remotely connecting to an existing blockchain network.
3. Research how to pass a configuration file to the code at runtime. Checkout the "Debugger Extension" at https://code.visualstudio.com/api/extension-guides/debugger-extension . Would it be possible to pass a runtime configuration file here? How to deal with such complexity when multiple configuration files are passed?

Define the outcomes and expectations from the project. This can cover requirements from the end users, the technical requirements that the project team can mandate based on feasibility study. At times the decision may also be done based on the collaboration with other project teams in open source.