@nqminds/nqm-tdx-terminal-cli v2.0.0

nqm-tdx-terminal-cli

Command-line interface for accessing the TDX API

Install

The best use of tdxcli tool is to install it with npm globally as follows:

npm i -g @nqminds/nqm-tdx-terminal-cli

The client app can be accessed by running the command tdxcli-node.

Binary packages

The tool is also packaged as a standalone binary package for Linux (Ubuntu/Debian), Windows and Mac OS X. The packages can be downloaded from the github repo Release.

• tdxcli - Linux executable
• tdxcli-macos - Mac OS X executable
• tdxcli.exe - Windows executable
• tdxcli_*.*-*.deb - Ubuntu/Debian installation package. After instalation the tool can be accessed by running the command tdxcli.

Usage

Usage: tdxcli-node <command> [options]

Commands:
  tdxcli-node signin [id] [secret]                   Sign in to tdx
  tdxcli-node signout                                Sign out of tdx
  tdxcli-node info [type] [id]                       Output current account info
  tdxcli-node config                                 Output tdx config
  tdxcli-node list [type]                            List all configured aliases or secrets
  tdxcli-node token <command>                        Get or revoke a token for a give alias
  tdxcli-node runapi <command>                       Run a tdx api command
  tdxcli-node download <rid> [filepath]              Download resource
  tdxcli-node upload <rid> <filepath>                Upload resource
  tdxcli-node copyalias <name>                       Makes a copy of an existing alias configuration
  tdxcli-node modifyalias <name> <config>            Modifies an existing alias configuration
  tdxcli-node removealias <name>                     Removes an existing alias configuration
  tdxcli-node databot <command> <id> [config]        Starts, stops or aborts a databot instance
  tdxcli-node deploy <id> <rid> <config> <filepath>  Deploys a databot stop->upload->start

Options:
  -a, --alias        Alias name                                                               [string]
  -c, --credentials  TDX credentials {id:"",secret:""} in base64                              [string]
  -t, --tdx-configs  The path to the TDX config file                                          [string]
  -j, --json         Output as json                                                          [boolean]
  -h, --help         Show help                                                               [boolean]
  -v, --version      Show version number                                                     [boolean]

Documentation

In order to use the tdxcli app one has to sign into a tdx account with an email address or share token (id and secret). If the user signs in using an email address the tdxcli will automatically open a Chromium browser window where the user can input the credentials. If the user signs in with an email id + secret the tdxcli app will open a headless Chromium window and will automatically fill in the credentials. Finally, if the user signs in with a share token the tdxcli will sign in using the tdx api authentication method.

Credentials

The user can signin automatically and run each tdxcli command except signin with a predefined secret in base64 of the form {"id": "", "secret": ""}. The credentials can be passed as a paramater together with a preconfigured alias name as follows:

tdxcli commandtoexecute ...variousparams --alias=name --credentials=secretinbase64

The credentials can also be passed as an environment variable as follows:

TDX_CREDENTIALS=secretinbase64 tdxcli commandtoexecute ...variousparams --alias=name

To get a credentials in base64 the user can sign in and retrieve the credentials with the below commands:

tdxcli signin id secret --alias=name
tdxcli list credentials

The output of the last command will show the stored credentials.

Tdx config file

One can also pass a custom tdx config file with param --tdx-config as follows:

tdxcli commandtoexecute ...variousparams --alias=name --tdx-config=pathtoconfig

The config file contains the tdx configuration for each defined alias as follows:

{
  "nqminds": {
    "tokenHref": "https://tbx.nqminds.com",
    "config": {
      "commandServer": "https://cmd.nqminds.com",
      "ddpServer": "https://ddp.nqminds.com",
      "queryServer": "https://q.nqminds.com",
      "tdxServer": "https://tdx.nqminds.com",
      "databotServer": "http://databot.nqminds.com",
      "accessTokenTTL": 31622400
    }
  },
  "nq_m": {
    "tokenHref": "https://tbx.nq-m.com",
    "config": {
      "commandServer": "https://cmd.nq-m.com",
      "ddpServer": "https://ddp.nq-m.com",
      "queryServer": "https://q.nq-m.com",
      "tdxServer": "https://tdx.nq-m.com",
      "databotServer": "http://databot.nq-m.com",
      "accessTokenTTL": 31622400
    }
  }
}

In the above example there are two defined aliases nqminds and nq-m.

Command outpout

To output the result of the command in a standardised json format use tdxcli with -j options as follows:

tdxcli -j commandtoexecute ...variousparams

signin

Usage

tdxcli signin
tdxcli signin emailorsharetokenid thesecret

The first command will open a Chromium browser window, wheares the second will do an automatic signin with the provided credentials. The obtained access token will be stored in the .env file.

Initially the user has to choose an alias in order to sign into a given tdx account. The default aliases are nqminds and nq_m, which correspond to tdx.nqminds.com and tdx.nq-m.com, respectively .

tdxcli signin --alias=nqminds
tdxcli signin emailorsharetokenid thesecret --alias=nq_m

Note, the aliases configurations are stored in config.json in home folder .tdxcli of the user. A new alias can be copied from an existing alias, it can be modified or removed.

The tdxcli signin allows storing access tokens and secrets for every configured alias. So, that the user can change among them by providing the tdxcli signin --alias=name option.

If the optins --alias is not provided tdxcli will use default alias name, which was obtained by previously running the command:

tdxcli signin --alias=name

Note, the sign in process will fail if using an email address with added security (for instance signing in with gmail + second factor authentication).

signout

Usage

tdxcli signout
tdxcli signout --alias=name

Sign out from the default alias or from the alias given by the name name. The command removes the stored access token and the secrets from .env file for default alias or the alias given by name name.

info

Usage

tdxcli info
tdxcli info account
tdxcli info serverfolderid appid
tdxcli info databotsid
tdxcli info appurl instanceid

The above command can also be run with the --alias option.

tdxcli info and tdxcli info account will output the account information corresponding to the signed in access token.

tdxcli info serverfolderid appid will return the server folder id for a given application id appid.

tdxcli info databotsid will return all databot ids.

tdxcli info appurl instanceid will return the app url for databot with instance instanceid.

config

Usage

tdxcli config
tdxcli config --alias=name

Outputs the current tdx config for the default or a given alias name name.

list

Usage

tdxcli list aliases
tdxcli list aliases --alias=name
tdxcli list secrets
tdxcli list secrets --alias=name

The first command lists all configured aliases. The second command lists all secrets in base64 for each configured alias.

runapi

Usage

tdxcli runapi getAccounts
tdxcli runapi getData --@1.a="testa" --@1.b="testb" --@2.result=1
tdxcli runapi getData --@1.a="1" --@1.b="testb" --@2.result=1 -- @1.a

The above commands can also be run with a given --alias options.

The runapi command executes a tdx api function. The argumets of the function are encoded using --@n, where n is the index of the argument starting from 1.

For instance getData(datasetId, filter, projection, options, ndJSON) has 5 arguments. The value of each argument can be encoded as --@1=value,--@2=value,--@3=value,--@4=value,--@5=value. If the value is an object then one can use the dot notation for encoding. For instance if the getData filter equals {a: {b: {c: 1}}} then it can be encoded as --@1.a.b.c=1.

Note, the command line parser tries to identify if an argument value is a number or not. So, if you pass --@1="12345" it will translate it into the number 12345. To solves this problem one has to use the -- symbol at the end of all argument definition and write an additional --@.1 signifying that the arguiment 1 should be kept as string. Below is the usage example

tdxcli runapi apicommand --@1.a="12345" -- @1.a

download

Usage

tdxcli download resourceid
tdxcli download resourceid outputfilename

The first command will download the resource and output it to stdout. Using this command one can save the resource into a file with tdxcli download someid >> outfile or pipe it into another bash command.

The second command will save the resource into a file given by the name outputfilename.

upload

Usage

tdxcli upload resourceid filetoupload

The above command uploads the file filetoupload into a resource given by the resourceid.

copyalias

Usage

tdxcli copyalias newalias
tdxcli copyalais newalias --alias=somealais

The first command makes a copy of the default alias configuration to a newalias configuration and saves it into config.json.

The second command makes a copy of somealias configuration to a newalias configuration and saves it into config.json

modifyalias

Usage

tdxcli modifyalias aliasname configfile.json

The above command modifies the aliasname configuration using the json from configfile.json and saves it to config.json.

Example config file configfile.json:

{
  "tokenHref": "https://tbx.nqminds.com",
  "config": {
    "commandServer": "https://cmd.nqminds.com",
    "ddpServer": "https://ddp.nqminds.com",
    "queryServer": "https://q.nqminds.com",
    "tdxServer": "https://tdx.nqminds.com",
    "accessTokenTTL": 31622400
  }
}

removealias

Usage

tdxcli removealias aliasname

The removes the aliasname from config.json.

databot

Usage

tdxcli databot start databotid databot.json
tdxcli databot stop databotinstanceid
tdxcli databot abort databotinstanceid

The first command starts an instance of the databot id databotid with the configuration file given by the file path databot.json.

Example databot instance start configuration file:

{
  "inputs": {
    "settings": {}
  },
  "id": "instanceid",
  "name": "somename",
  "overwriteExisting": "instanceid",
  "schedule": {
    "always": true
  },
  "shareKeyId": "someappid",
  "shareKeySecret": "somesecret",
}

The second command stops the databot with the instance id databotinstanceid and the third command aborts the databot with the instance id databotinstanceid.

token

Usage

tdxcli token get

The command returns the access token for a the default alias or an alias passed with --alias.

deploy

Usage

tdxcli deploy databotid resourceid databot.json filetoupload

The above command will deploy a databot with the following steps:

1 Will stop a running databot instance with the databot instance id from config file databot.json.

2 Will upload the file filetoupload to tdx resource id resourceid.

3 Will start a new databot instance id for the databot databotid.