Ewasm CLI - Development Workflow

[Latrasis]

Based on #188, we need a basic deployment workflow via the CLI.

Compile a hello_world procedure

Assuming the project:

• Has a deployed kernel instance
• Has a default acl entry procedure
• Has a default admin procedure and the account is an admin

User should:

1. Create a new cargo lib in project folder
2. Set Correct Dependencies
3. Compile to Wasm

Deploy a new Procedure

Assuming the project:

• Has a deployed kernel instance
• Has a default acl entry procedure
• Has a default admin procedure and the account is an admin
• User has a .wasm file for the new procedure - not pre-processed

A cli command should:

1. Receive the.wasm file
2. Process the .wasm file
3. Deploy / Create the procedure contract
4. Return the procedure address

Register a new Procedure

Assuming the project:

• Has a deployed kernel instance
• Has a default acl entry procedure
• Has a default admin procedure and the account is an admin
• User has the address with the deployed contract procedure
• User has a capability-list file for the new procedure
• User has an Id for the new procedure

A cli command should:

1. Register the the procedure with given id and caplist

Call a new Procedure

Assuming the project:

• Has a deployed kernel instance
• Has a default acl entry procedure
• Has a default admin procedure and the account is an admin
• The admin procedure can call to the procedure id

A cli command should:

1. Recieve an procedure id name
2. Receive an abi function name
3. Recieve an argument list in brackets

cap9 exec <group_id> <proc_id> <method> [param1, param2, ... ]

[JakeOShannessy]

Slight changes to the function execution command. The most significant is that the current example ACL model does not have a concept of "calling a procedure". The model of the ACL is that each user is forwarded to a procedure dedicated to their group which acts as a sandbox which defines everything they can do. There fore the <proc_id> and <group_id> parts are currently omitted.

Instead of exec we have call and query to reflect that there are two different modes of execution and we are likely to want to take advantage of both.

Also the parameters are not in brackets as it is not necessary for disambiguation and is simpler to parse.

Execution now looks like this:

cap9 call <method> <params...>

or

cap9 query <method> <params...>