Setting up cli interactive flow

[jamiehewitt15]

Fixes #70

Changes proposed in this PR:

• Setting up cli interactive flow
• Publishing asset
• Adding interactive flow to the system tests.

To test (with barge):

1. run barge locally
2. run ocean node locally
3. set the envs in ocean-cli (export NODE_URL="http://127.0.0.1:8001"). No need to set Aquarius or provider URL anymore.
4. npm run build && npm run cli start

To test (with Oasis testnet):

1. get rose tokens on the testnet using the faucet: https://faucet.testnet.oasis.dev
2. Run the node with oasis tesnet in the RPC env: export RPCS='{ "23295":{ "rpc":"https://testnet.sapphire.oasis.io", "chainId": 23295, "network": "sapphire-testnet", "chunkSize": 1000 }}'
3. set the envs in ocean-cli (export NODE_URL="http://127.0.0.1:8001"). No need to set Aquarius or provider URL anymore.
4. npm run build && npm run cli start

[mihaisc]

can you do a quick update on the environment vars, so we don't have provider, aquarius

[paulo-ocean]

Lgtm.
One small comment, as we are not using the createAsset from SDK
This part:

ddo.services[0].files = await ProviderInstance.encrypt(
		assetUrl,
		chainId,
		macOsProviderUrl || providerUrl
	);

If the templateIndex is 4
we need to remove the files object from the ddo service (actually we need to set it to empty string, not null, due to schema validations)
Like this

if(templateIndex === 4){ 
  ddo.services[0].files = ''
 } else ...

[jamiehewitt15]

we need to remove the files object from the ddo service (actually we need to set it to empty string, not null, due to schema validations)

Ok, thanks for letting me know. I'll adjust that.

[jamiehewitt15]

@paulo-ocean I've updated it to set the files as an empty string for template index 4. Let me know if it's alright and I'll merge this

[paulo-ocean]

@paulo-ocean I've updated it to set the files as an empty string for template index 4. Let me know if it's alright and I'll merge this

go for it