bluerainsoftware / id4i-cli Goto Github PK

Currently, we support only https.
If we want to use the CLI locally during development, we need to change the transport config and build a version that uses it.
Alternatively, we could make it switchable, but no one other then us will need it, so I'd probably opt for a forked dev version.
WDYT?

• Take a look at bats
• Generate user w/ API key on develop (existing UI tests or curl)
• Have a shell script using the cli to carry out all operations
• Have the script run in CI

Use current swagger spec, operation in question is https://id4i-develop.herokuapp.com/docs/redoc/index.html#operation/receive

Tests (currently skipped): test/tests/transfer.bats:44 & test/tests/transfer.bats:56

Currently, we just log the error directly. e.g.: time="2018-12-04T12:57:26+01:00" level=error msg="[POST /api/v1/guids][401] createGuidUnauthorized &{Code:0xc0001f8050 ErrorID:0xc0001f8080 ErrorList:[] Message:0xc0001f8060}"

We should log a JSON representation of the API error as well as all request parameters and headers.

Add shell completion script generation commands for

• bash
• zsh

References:

• https://github.com/spf13/cobra/blob/master/bash_completions.md
• https://debian-administration.org/article/316/An_introduction_to_bash_completion_part_1
• https://kubernetes.io/docs/tasks/tools/install-kubectl/#enabling-shell-autocompletion

Currently, users, API keys, and the resulting id4i-cli config come from id4i-develop. This is hard-coded in test/preflight.sh.

We need to make this target system URL configurable.

• Change label
• Remove elements
• Add elements

• Create Collection
• Read Collection Contents
• Delete Collection
• [ ] Update Collection Label -> #27