Skip to content
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

Research command capability of VS Code extension #4

Open
arsulegai opened this issue Feb 6, 2024 · 0 comments
Open

Research command capability of VS Code extension #4

arsulegai opened this issue Feb 6, 2024 · 0 comments

Comments

@arsulegai
Copy link
Member

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.
@arsulegai arsulegai converted this from a draft issue Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant