asperalm 0.8.10 → 0.9

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 1c27eddfbfc538d221dec82b0afcb7943fce33887ccfb03f8d12f504d0bbf03e
4
- data.tar.gz: 4c78e96a41a69314b94fe41c2869a463a515e37de8c51293d62ccf9557fca4fb
3
+ metadata.gz: 9f09af42c6df45bc6d62d92a61368675234181a253cbc2a0b718592b2f61c21a
4
+ data.tar.gz: aec1729de528244d26527df19c123a0bf308019a4cef1e20d08a9a4fc0283740
5
5
  SHA512:
6
- metadata.gz: bfab0b8e7552254c511fc5765f17bda97cd7f2608b7e2e173f5a1196031fa27430a494f0ab06148c98bb2519c02cfcac915c62f6359d9632825699d1852e9ea2
7
- data.tar.gz: 9f84387700cd9b71f2b837220a0dbc065f88bc7c997c0c828aa8ebe1ed54d36d83841ad2d0995ea598d6f3d4fb8c438446cd5f1f510e8a6e79031cf69a909fa9
6
+ metadata.gz: 16f58f1a2c713f1f3fa377592b9253892966da5af0152782fdf859e85d3ae1c1dfc3cf14ceb4a14db1eac3fe391defa658991a8455fa946194088b7401454d2c
7
+ data.tar.gz: e46f5259f71880cb7010c65e6e2a9d3c36f34277dbac325d952e7bbb732787fc1e29a6b387b6bfdd71c603d6fb6f18cc41110459e4321f94709deacf8b0db88c
data/README.md CHANGED
@@ -1,6 +1,8 @@
1
- # Asperalm - Laurent's Aspera Command Line Interface and Ruby Library
1
+ # Asperalm - Laurent's IBM Aspera Command Line Interface and Ruby Library
2
+
3
+ Version : 0.9
4
+
2
5
 
3
- Version : 0.8.10
4
6
 
5
7
 
6
8
  _Laurent/2016-2018_
@@ -15,13 +17,14 @@ Disclaimers:
15
17
  * Use at your risk (not in production environments)
16
18
  * This gem is provided as-is, and is not intended to be
17
19
  a complete CLI, or industry-grade product.
20
+ * some features may not be fully validated
18
21
  * IBM provides an officially supported Aspera CLI: [http://downloads.asperasoft.com/en/downloads/62](http://downloads.asperasoft.com/en/downloads/62) .
19
22
 
20
- That being said, the `aslmcli` tool is very powerful and gets things done, it's also a great tool to learn Aspera APIs.
23
+ That being said, `mlia` is very powerful and gets things done, it's also a great tool to learn Aspera APIs.
21
24
 
22
25
  This manual addresses three parts:
23
26
 
24
- * `aslmcli` : command line interface to Aspera
27
+ * `mlia` : ("Amelia") command line interface to Aspera
25
28
  * `asession` : starting a FASP Session with JSON parameters
26
29
  * `Asperalm` : includes a Ruby "FASPManager"
27
30
 
@@ -29,24 +32,23 @@ In examples, command line operations (starting with `$`) are shown using a stand
29
32
 
30
33
  # Quick Start
31
34
 
32
- To start using the `aslmcli` tool, follow the section: [Installation](#installation) (Ruby, Gem, FASP).
35
+ First, follow the section: [Installation](#installation) (Ruby, Gem, FASP) to start using `mlia`.
33
36
 
34
- Once the gem is installed, the `aslmcli` shall be accessible:
37
+ Once the gem is installed, `mlia` shall be accessible:
35
38
 
36
39
  ```bash
37
- $ aslmcli --version
38
- 0.8.10
39
-
40
+ $ mlia --version
41
+ 0.9
40
42
  ```
41
43
 
42
44
  ## First use
43
45
 
44
- Once installation is completed, you can proceed to the first sample use with a demo server:
46
+ Once installation is completed, you can proceed to the first use with a demo server:
45
47
 
46
48
  One liner:
47
49
 
48
50
  ```
49
- $ aslmcli server browse / --url=ssh://demo.asperasoft.com:33001 --username=asperaweb --password=demoaspera
51
+ $ mlia server browse / --url=ssh://demo.asperasoft.com:33001 --username=asperaweb --password=demoaspera
50
52
  :............:...........:......:........:...........................:.......................:
51
53
  : zmode : zuid : zgid : size : mtime : name :
52
54
  :............:...........:......:........:...........................:.......................:
@@ -65,11 +67,11 @@ In order to make further calls more convenient, it is advised to define a "param
65
67
  * download a file
66
68
 
67
69
  ```
68
- $ aslmcli config id demoserver update --url=ssh://demo.asperasoft.com:33001 --username=asperaweb --password=demoaspera
70
+ $ mlia config id demoserver update --url=ssh://demo.asperasoft.com:33001 --username=asperaweb --password=demoaspera
69
71
  updated: demoserver
70
- $ aslmcli config id default set server demoserver
72
+ $ mlia config id default set server demoserver
71
73
  updated: default->server to demoserver
72
- $ aslmcli server browse /aspera-test-dir-large
74
+ $ mlia server browse /aspera-test-dir-large
73
75
  :............:...........:......:..............:...........................:............................:
74
76
  : zmode : zuid : zgid : size : mtime : name :
75
77
  :............:...........:......:..............:...........................:............................:
@@ -86,7 +88,7 @@ $ aslmcli server browse /aspera-test-dir-large
86
88
  : -rw-r--r-- : asperaweb : fasp : 104857600 : 2014-04-10 19:49:29 +0200 : 100MB :
87
89
  : -rw-r--r-- : asperaweb : fasp : 10737418240 : 2014-04-10 19:49:04 +0200 : 10GB :
88
90
  :............:...........:......:..............:...........................:............................:
89
- $ aslmcli server download /aspera-test-dir-large/200MB
91
+ $ mlia server download /aspera-test-dir-large/200MB
90
92
  Time: 00:00:02 ========================================================================================================== 100% 100 Mbps Time: 00:00:00
91
93
  complete
92
94
  ```
@@ -98,7 +100,7 @@ Note that browse and download commans are shorter now.
98
100
  Get familiar with configuration, options, parameters and
99
101
  follow the section relative to the product you want to interact with: Aspera on Cloud, Faspex, ...
100
102
 
101
- Detailed generic information on configuration can be found in section: [aslmcli](#aslmcli).
103
+ Detailed generic information on configuration can be found in section: [Command Line Interface](#cli).
102
104
 
103
105
  # <a name="installation"></a>Installation
104
106
 
@@ -163,25 +165,23 @@ Most file transfers will be done using the FASP protocol. This requires one of I
163
165
  For instance, Aspera Connect Client can be installed
164
166
  by visiting the page: [http://downloads.asperasoft.com/connect2/](http://downloads.asperasoft.com/connect2/).
165
167
 
166
- `aslmcli` will detect most of Aspera transfer products in standard locations and use the first one found. Refer to section [Client](#client) for details.
168
+ `mlia` will detect most of Aspera transfer products in standard locations and use the first one found. Refer to section [Client](#client) for details.
167
169
 
168
170
  Several methods are provided on how to effectively start a transfer, refer to section: [Transfer Agents](#agents)
169
171
 
170
- # <a name="aslmcli"></a>Tool: `aslmcli`
172
+ # <a name="cli"></a>Command Line Interface: `mlia`
171
173
 
172
174
  The `asperalm` Gem provides a command line interface (CLI) which interacts with Aspera Products (mostly REST APIs):
173
175
 
174
- * Aspera on Cloud
175
- * Faspex
176
- * Server
177
- * Node
178
- * Shares
179
- * Console
180
- * Orchestrator
181
- * ATS
176
+ * IBM Aspera High Speed Transfer Server (FASP and Node)
177
+ * IBM Aspera on Cloud (including ATS)
178
+ * IBM Aspera Faspex
179
+ * IBM Aspera Shares
180
+ * IBM Aspera Console
181
+ * IBM Aspera Orchestrator
182
182
  * and more...
183
183
 
184
- `aslmcli` provides the following features:
184
+ `mlia` provides the following features:
185
185
 
186
186
  * Supports most Aspera server products (on-premise and SaaS)
187
187
  * Options can be provided on command line, in configuration file, in env var, in files (products URL, credentials or any option)
@@ -198,19 +198,19 @@ The `asperalm` Gem provides a command line interface (CLI) which interacts with
198
198
  Basic usage is displayed by executing:
199
199
 
200
200
  ```bash
201
- $ aslmcli -h
201
+ $ mlia -h
202
202
  ```
203
203
 
204
- Refer to sections: [Usage](#usage) and [Sample Commands](commands).
204
+ Refer to sections: [Usage](#usage) and [Sample Commands](#commands).
205
205
 
206
- Not all `aslmcli` features are fully documented here, the user may explore commands on the command line.
206
+ Not all `mlia` features are fully documented here, the user may explore commands on the command line.
207
207
 
208
208
  ## Commands, Arguments and Options
209
209
 
210
210
  Commands, Options and Arguments are typically provided on command line, e.g. in:
211
211
 
212
212
  ```
213
- $ aslmcli command --option-name=VAL1 VAL2
213
+ $ mlia command --option-name=VAL1 VAL2
214
214
  ```
215
215
 
216
216
  * executes action: `command`
@@ -218,7 +218,7 @@ $ aslmcli command --option-name=VAL1 VAL2
218
218
  * this option has a value of: `VAL1`
219
219
  * the command has one argument: `VAL2`
220
220
 
221
- When the value of a command, option or argument is constrained by a fixed list of values, it is possible to use the first letters of the value only, provided that it uniquely identifies a value. For example `aslmcli conf ov` is the same as `aslmcli config overview`.
221
+ When the value of a command, option or argument is constrained by a fixed list of values, it is possible to use the first letters of the value only, provided that it uniquely identifies a value. For example `$ mlia conf ov` is the same as `$ mlia config overview`.
222
222
 
223
223
  The value of options and arguments is evaluated with the [Extended Value Syntax](#extended).
224
224
 
@@ -238,7 +238,7 @@ Exceptions:
238
238
  * the special option `--` stops option processing and is ignored, following command line arguments are taken as arguments, including the ones starting with a `-`. Example:
239
239
 
240
240
  ```
241
- $ aslmcli config echo -- --sample
241
+ $ mlia config echo -- --sample
242
242
  "--sample"
243
243
  ```
244
244
 
@@ -252,10 +252,10 @@ The value for _any_ options can come from the following locations (in this order
252
252
  * Environment variable
253
253
  * Command line
254
254
 
255
- Environment variable starting with prefix: ASLMCLI_ are taken as option values,
256
- e.g. `ASLMCLI_OPTION_NAME` is for `--option-name`.
255
+ Environment variable starting with prefix: MLIA_ are taken as option values,
256
+ e.g. `MLIA_OPTION_NAME` is for `--option-name`.
257
257
 
258
- Options values can be displayed for a given command by providing the `--show-config` option: `aslmcli node --show-config`
258
+ Options values can be displayed for a given command by providing the `--show-config` option: `$ mlia node --show-config`
259
259
 
260
260
  ### Commands and Arguments
261
261
 
@@ -298,7 +298,7 @@ The style of output can be set using the `format` parameter, supporting:
298
298
  Table output can be filtered using the `select` parameter. Example:
299
299
 
300
300
  ```
301
- $ aslmcli aspera admin res user list --fields=name,email,ats_admin --query=@json:'{"per_page":1000}' --select=@json:'{"ats_admin":true}'
301
+ $ mlia aspera admin res user list --fields=name,email,ats_admin --query=@json:'{"per_page":1000}' --select=@json:'{"ats_admin":true}'
302
302
  :...............................:..................................:...........:
303
303
  : name : email : ats_admin :
304
304
  :...............................:..................................:...........:
@@ -339,13 +339,13 @@ To display the result of an extended value, use the `config echo` command.
339
339
  Example: read the content of the specified file, then, base64 decode, then unzip:
340
340
 
341
341
  ```bash
342
- $ aslmcli config echo @zlib:@base64:@file:myfile.dat
342
+ $ mlia config echo @zlib:@base64:@file:myfile.dat
343
343
  ```
344
344
 
345
345
  Example: create a value as a hash, with one key and the value is read from a file:
346
346
 
347
347
  ```bash
348
- $ aslmcli config echo @ruby:'{"token_verification_key"=>File.read("pubkey.txt")}'
348
+ $ mlia config echo @ruby:'{"token_verification_key"=>File.read("pubkey.txt")}'
349
349
  ```
350
350
 
351
351
  Example: read a csv file and create a list of hash for bulk provisioning:
@@ -355,7 +355,7 @@ $ cat test.csv
355
355
  name,email
356
356
  lolo,laurent@example.com
357
357
  toto,titi@tutu.tata
358
- $ aslmcli config echo @csvt:@file:test.csv
358
+ $ mlia config echo @csvt:@file:test.csv
359
359
  :......:.....................:
360
360
  : name : email :
361
361
  :......:.....................:
@@ -368,7 +368,7 @@ $ aslmcli config echo @csvt:@file:test.csv
368
368
 
369
369
  Some options and parameters expect a _Structured Value_, i.e. a value more complex than a simple string. This is usually a Hash table or an Array, which could also contain sub structures.
370
370
 
371
- For instance, a [_transfer-spec_](#_transferspec_) is expected to be a _Structured Value_.
371
+ For instance, a [_transfer-spec_](#transferspec) is expected to be a _Structured Value_.
372
372
 
373
373
  Structured values shall be described using the [Extended Value Syntax](#extended).
374
374
  A convenient way to specify a _Structured Value_ is to use the `@json:` decoder, and describe the value in JSON format. The `@ruby:` decoder can also be used. For an array of hash tables, the `@csvt:` decoder can be used.
@@ -377,7 +377,7 @@ It is also possible to provide a _Structured Value_ in a file using `@json:@file
377
377
 
378
378
  ## <a name="configfile"></a>Configuration file
379
379
 
380
- `aslmcli` configuration and cache files are stored in folder `$HOME/.aspera/aslmcli`.
380
+ `mlia` configuration and cache files are stored in folder `$HOME/.aspera/$ mlia`.
381
381
 
382
382
  A configuration file is created with configuration modification commands. There is no mandatory information required in this file. It is mainly used to define pre-sets of command options.
383
383
 
@@ -385,7 +385,7 @@ All options can be set on command line, or by env vars, or in the configuratin f
385
385
  A configuration file provides a way to define default values, especially
386
386
  for authentication parameters, thus avoiding to always have to specify those parameters on the command line.
387
387
 
388
- The default configuration file is: `$HOME/.aspera/aslmcli/config.yaml`
388
+ The default configuration file is: `$HOME/.aspera/$ mlia/config.yaml`
389
389
  (this can be overriden with option `--config-file=path`).
390
390
 
391
391
  It is composed of _option presets_ containing pre-sets for options.
@@ -395,13 +395,13 @@ It is composed of _option presets_ containing pre-sets for options.
395
395
  The configuration file can be modified using the following commands:
396
396
 
397
397
  ```
398
- aslmcli config id <option preset> set|delete|show|initialize|update
398
+ $ mlia config id <option preset> set|delete|show|initialize|update
399
399
  ```
400
400
 
401
401
  The command `update` allows the easy creation of option preset by simply providing the options in their command line format, e.g. :
402
402
 
403
403
  ```
404
- aslmcli config id node_to_node update --url=https://10.25.0.4:9092 --username=node_user --password=node_pass --ts=@json:'{"precalculate_job_size":true}' --transfer=node --transfer-node=@json:'{"url":"https://10.25.0.8:9092","username":"node_user2","password":"node_pass2"}'
404
+ $ mlia config id node_to_node update --url=https://10.25.0.4:9092 --username=node_user --password=node_pass --ts=@json:'{"precalculate_job_size":true}' --transfer=node --transfer-node=@json:'{"url":"https://10.25.0.8:9092","username":"node_user2","password":"node_pass2"}'
405
405
  ```
406
406
 
407
407
  * This creates a _option preset_ `node_to_node` with all provided options.
@@ -414,13 +414,13 @@ A good practice is to not manually edit this file and use modification commands.
414
414
  If necessary, the configuration file can be edited (or simply consulted) with:
415
415
 
416
416
  ```bash
417
- $ aslmcli config open
417
+ $ mlia config open
418
418
  ```
419
419
 
420
420
  A full terminal based overview of the configuration can be displayed using:
421
421
 
422
422
  ```bash
423
- $ aslmcli config over
423
+ $ mlia config over
424
424
  ```
425
425
 
426
426
 
@@ -448,7 +448,7 @@ Configuation is organized in _option presets_, like in `.ini` files. Each group
448
448
 
449
449
  Two _option presets_ are reserved:
450
450
 
451
- * `config` is reserved for the global parameters of the `aslmcli` tool.
451
+ * `config` is reserved for the global parameters of `mlia`.
452
452
  It contains a special parameter: "version" showing the CLI
453
453
  version used to create this file. It is used to check compatibility.
454
454
  * `default` is reserved to define the default option preset name used for plugins.
@@ -461,7 +461,7 @@ Values in the configuration also follow the [Extended Value Syntax](#extended).
461
461
  Note: if the user wants to use the [Extended Value Syntax](#extended) inside the configuration file, using the `config id update` command, the user shall use the `@val:` prefix. Example:
462
462
 
463
463
  ```bash
464
- $ aslmcli config id my_aoc_org set private_key @val:@file:"$HOME/.aspera/aslmcli/aocapikey"
464
+ $ mlia config id my_aoc_org set private_key @val:@file:"$HOME/.aspera/$ mlia/aocapikey"
465
465
  ```
466
466
 
467
467
  This creates the _option preset_:
@@ -469,7 +469,7 @@ This creates the _option preset_:
469
469
  ```
470
470
  ...
471
471
  my_aoc_org:
472
- private_key: @file:"/Users/laurent/.aspera/aslmcli/aocapikey"
472
+ private_key: @file:"/Users/laurent/.aspera/$ mlia/aocapikey"
473
473
  ...
474
474
  ```
475
475
 
@@ -497,14 +497,14 @@ The main plugin name is *config*, so it is possible to define a default preset f
497
497
  the main plugin with:
498
498
 
499
499
  ```
500
- $ aslmcli config id cli_default set interactive no
501
- $ aslmcli config id default set config cli_default
500
+ $ mlia config id cli_default set interactive no
501
+ $ mlia config id default set config cli_default
502
502
  ```
503
503
 
504
504
  A preset value can be removed with `unset`:
505
505
 
506
506
  ```
507
- $ aslmcli config id cli_default unset interactive
507
+ $ mlia config id cli_default unset interactive
508
508
  ```
509
509
 
510
510
 
@@ -515,25 +515,25 @@ only username/password and url are required (either on command line, or from con
515
515
  Those can usually be provided on the command line:
516
516
 
517
517
  ```bash
518
- $ aslmcli shares repo browse / --url=https://10.25.0.6 --username=john --password=4sp3ra
518
+ $ mlia shares repo browse / --url=https://10.25.0.6 --username=john --password=4sp3ra
519
519
  ```
520
520
 
521
521
  This can also be provisioned in a config file:
522
522
 
523
523
  ```bash
524
- 1$ aslmcli config id shares06 set url https://10.25.0.6
525
- 2$ aslmcli config id shares06 set username john
526
- 3$ aslmcli config id shares06 set password 4sp3ra
527
- 4$ aslmcli config id default set shares shares06
528
- 5$ aslmcli config overview
529
- 6$ aslmcli shares repo browse /
524
+ 1$ mlia config id shares06 set url https://10.25.0.6
525
+ 2$ mlia config id shares06 set username john
526
+ 3$ mlia config id shares06 set password 4sp3ra
527
+ 4$ mlia config id default set shares shares06
528
+ 5$ mlia config overview
529
+ 6$ mlia shares repo browse /
530
530
  ```
531
531
 
532
532
  The three first commands build a option preset.
533
533
  Note that this can also be done with one single command:
534
534
 
535
535
  ```bash
536
- $ aslmcli config id shares06 init @json:'{"url":"https://10.25.0.6","username":"john","password":"4sp3ra"}'
536
+ $ mlia config id shares06 init @json:'{"url":"https://10.25.0.6","username":"john","password":"4sp3ra"}'
537
537
  ```
538
538
 
539
539
  The fourth command defines this option preset as the default option preset for the
@@ -546,13 +546,13 @@ Eventually, the last command shows a call to the shares application using defaul
546
546
 
547
547
  ## Plugins
548
548
 
549
- The CLI tool uses a plugin mechanism. The first level command (just after `aslmcli` on the command line) is the name of the concerned plugin which will execute the command. Each plugin usually represent commands sent to a specific application.
549
+ The CLI tool uses a plugin mechanism. The first level command (just after `mlia` on the command line) is the name of the concerned plugin which will execute the command. Each plugin usually represent commands sent to a specific application.
550
550
  For instance, the plugin "faspex" allows operations on the application "Aspera Faspex".
551
551
 
552
552
  ### Create your own plugin
553
553
  ```bash
554
- $ mkdir -p ~/.aspera/aslmcli/plugins
555
- $ cat<<EOF>~/.aspera/aslmcli/plugins/test.rb
554
+ $ mkdir -p ~/.aspera/$ mlia/plugins
555
+ $ cat<<EOF>~/.aspera/$ mlia/plugins/test.rb
556
556
  require 'asperalm/cli/plugin'
557
557
  module Asperalm
558
558
  module Cli
@@ -570,7 +570,7 @@ EOF
570
570
 
571
571
  ## Debugging
572
572
 
573
- The gem is equipped with traces. By default logging level is "warn". To increase debug level, use parameter `log_level`, so either command line `--log-level=xx` or env var `ASLMCLI_LOG_LEVEL`.
573
+ The gem is equipped with traces. By default logging level is "warn". To increase debug level, use parameter `log_level`, so either command line `--log-level=xx` or env var `MLIA_LOG_LEVEL`.
574
574
 
575
575
  ## Learning Aspera Product APIs (REST)
576
576
 
@@ -606,18 +606,18 @@ This transfer can be done using on of the 3 following methods:
606
606
  * `connect` to make use of a local Connect Client
607
607
  * `node` to make use of a _remote_ Aspera Transfer Node.
608
608
 
609
- `aslmcli` standadizes on the use of a [_transfer-spec_](#_transferspec_) instead of _raw_ ascp options to provide parameters for a transfer session, as a common method for those three Transfer Agents.
609
+ `mlia` standadizes on the use of a [_transfer-spec_](#transferspec) instead of _raw_ ascp options to provide parameters for a transfer session, as a common method for those three Transfer Agents.
610
610
 
611
611
 
612
612
  ### <a name="agents"></a>Direct (local ascp using FASPManager API)
613
613
 
614
614
  By default the CLI will use a local FASP protocol.
615
- `aslmcli` will detect locally installed Aspera products.
615
+ `mlia` will detect locally installed Aspera products.
616
616
  Refer to section [Client](#client).
617
617
 
618
618
  ### IBM Aspera Connect Client GUI
619
619
 
620
- By specifying option: `--transfer=connect`, `aslmcli` will start transfers
620
+ By specifying option: `--transfer=connect`, `mlia` will start transfers
621
621
  using the locally installed Aspera Connect Client.
622
622
 
623
623
  ### Aspera Node API : Node to node transfers
@@ -646,107 +646,34 @@ is described in a _transfer-spec_ (Transfer Specification), such as:
646
646
  * file list
647
647
  * etc...
648
648
 
649
- `aslmcli` builds a default _transfer-spec_ internally, so it is not necessary to provide additional parameters on the command line for this transfer.
649
+ `mlia` builds a default _transfer-spec_ internally, so it is not necessary to provide additional parameters on the command line for this transfer.
650
650
 
651
651
  If needed, it is possible to modify or add any of the supported _transfer-spec_ parameter using the `ts` option. The `ts` option accepts a [Structured Value](#native) containing one or several _transfer-spec_ parameters.
652
652
 
653
- It is possible to specify ascp options when the `transfer` option is set to `direct` using the special [_transfer-spec_](#_transferspec_) parameter: `EX_ascp_args`. Example: `--ts=@json:'{"EX_ascp_args":["-l","100m"]}'`.
653
+ It is possible to specify ascp options when the `transfer` option is set to `direct` using the special [_transfer-spec_](#transferspec) parameter: `EX_ascp_args`. Example: `--ts=@json:'{"EX_ascp_args":["-l","100m"]}'`.
654
654
 
655
655
  The use of a _transfer-spec_ instead of `ascp` parameters has the advantage of:
656
656
 
657
657
  * common to all [Transfer Agent](#agents)
658
658
  * not dependant on command line limitations (special characters...)
659
659
 
660
- A [_transfer-spec_](#_transferspec_) is a Hash table, so it is described on the command line with the [Extended Value Syntax](#extended). Keys are described in section [Transfer Parameters](#transferparams).
661
-
662
- ### <a name="transferparams">Transfer Parameters
663
-
664
- All standard [_transfer-spec_](#_transferspec_) parameter can be overloaded. To display parameter,
665
- run in debug mode (--log-level=debug). [_transfer-spec_](#_transferspec_) can also be saved/overridden in
666
- the config file.
667
-
668
- (UNDER CONSTRUCTION <a href="https://developer.asperasoft.com/web/node/ops-transfers">ref</a>)
669
-
670
- * F=Fasp Manager(local FASP execution)
671
- * N=remote node(node API)
672
- * C=Connect Client(web plugin)
660
+ A [_transfer-spec_](#transferspec) is a Hash table, so it is described on the command line with the [Extended Value Syntax](#extended).
673
661
 
674
- Req/Def : Required or default value (- means emty)
662
+ <a name="transferparams"></a>
663
+ _transfer-spec_ parameters are described in this document: [Transfer Parameters](docs/transfer_spec.html).
675
664
 
676
- Fields with EX_ prefix are specific to aslmcli in local mode.
677
-
678
- arg: related ascp argument or env var suffix (PASS for ASPERA_SCP_PASS)
679
-
680
- <style type="text/css">
681
- table {border-collapse: collapse;}
682
- table, th, td {border: 1px solid black;}
683
- .yes {color:white;background-color:green;font-weight:bold;}
684
- .no {color:white;background-color:red;font-weight:bold;}
685
- </style>
686
- <table>
687
- <tr><th>Field</th><th>Req/Def</th><th>Type</th><th>F</th><th>N</th><th>C</th><th>arg</th><th>Description</th></tr>
688
- <tr><td>direction</td><td>Required</td><td>string</td><td class="yes">Y</td><td class="yes">Y</td><td class="yes">Y</td><td>--mode</td><td>Direction: "send" or "receive"</td></tr>
689
- <tr><td>remote_host</td><td>Required</td><td>string</td><td class="yes">Y</td><td class="yes">Y</td><td class="yes">Y</td><td>--host</td><td>IP or fully qualified domain name of the remote server</td></tr>
690
- <tr><td>remote_user</td><td>Required</td><td>string</td></td><td class="yes">Y</td><td class="yes">Y</td><td class="yes">Y</td><td>--user</td><td>Remote user. Default value is "xfer" on node or connect.</td></tr>
691
- <tr><td>destination_root</td><td>Required</td><td>string</td><td class="yes">Y</td><td class="yes">Y</td><td class="yes">Y</td><td>last arg</td><td>Destination root directory.</td></tr>
692
- <tr><td>title</td><td>-</td><td>string</td><td class="no">N</td><td class="yes">Y</td><td class="yes">Y</td><td>-</td><td>Title of the transfer</td></tr>
693
- <tr><td>tags</td><td>-</td><td>hash</td><td class="yes">Y</td><td class="yes">Y</td><td class="yes">Y</td><td>--tags<br>--tags64</td><td>Metadata for transfer</td></tr>
694
- <tr><td>token</td><td>-</td><td>string</td><td class="yes">Y</td><td class="yes">Y</td><td class="yes">Y</td><td>TOKEN<br/>-W</td><td>Authorization token: Bearer, Basic or ATM</td></tr>
695
- <tr><td>cookie</td><td>-</td><td>string</td><td class="yes">Y</td><td class="yes">Y</td><td class="yes">Y</td><td>COOKIE</td><td>Metadata for transfer (older,string)</td></tr>
696
- <tr><td>remote_access_key</td><td>TODO</td><td>string</td><td></td><td></td><td></td><td>?</td><td>Node only?</td></tr>
697
- <tr><td>source_root</td><td>-</td><td>string</td><td></td><td></td><td></td><td>--source-prefix<br/>--source-prefix64</td><td>Source root directory.(TODO: verify option)</td></tr>
698
- <tr><td>fasp_port</td><td>33001</td><td>integer</td></td><td class="yes">Y</td><td class="yes">Y</td><td class="yes">Y</td><td>-O</td><td>Specifies fasp (UDP) port.</td></tr>
699
- <tr><td>ssh_port</td><td>22 or 33001</td><td>integer</td></td><td class="yes">Y</td><td class="yes">Y</td><td class="yes">Y</td><td>-P</td><td>Specifies ssh (TCP) port.</td></tr>
700
- <tr><td>rate_policy</td><td>server config</td><td>string</td><td class="yes">Y</td><td class="yes">Y</td><td class="yes">Y</td><td>--policy</td><td>Valid literals include "low","fair","high" and "fixed".</td></tr>
701
- <tr><td>symlink_policy</td><td>follow</td><td>string</td><td class="yes">Y</td><td class="yes">Y</td><td class="yes">Y</td><td>--symbolic-links</td><td>copy, follow, copy+force, skip. Default is follow. Handle source side symbolic links by following the link (follow), copying the link itself (copy), skipping (skip), or forcibly copying the link itself (copy+force).</td></tr>
702
- <tr><td>target_rate_kbps</td><td>-</td><td>integer</td><td class="yes">Y</td><td class="yes">Y</td><td class="yes">Y</td><td>-l</td><td>Specifies desired speed for the transfer.</td></tr>
703
- <tr><td>min_rate_kbps</td><td>0</td><td>integer</td><td class="yes">Y</td><td class="yes">Y</td><td class="yes">Y</td><td>-m</td><td>Set the minimum transfer rate in kilobits per second.</td></tr>
704
- <tr><td>cipher</td><td>none</td><td>string</td><td class="yes">Y</td><td class="yes">Y</td><td class="yes">Y</td><td>-c</td><td>in transit encryption type.<br/>none, aes-128, aes-256</td></tr>
705
- <tr><td>content_protection</td><td>encrypt<br/>decrypt</td><td>string</td><td></td><td></td><td></td><td>--file-crypt=</td><td>encryption at rest</td></tr>
706
- <tr><td>content_protection_password</td><td>-</td><td>string</td><td></td><td></td><td></td><td>PASS</td><td>Specifies a string password.</td></tr>
707
- <tr><td>overwrite</td><td>diff</td><td>string</td><td class="yes">Y</td><td class="yes">Y</td><td class="yes">Y</td><td>--overwrite</td><td>Overwrite destination files with the source files of the same name.<br/>never, always, diff, older, or diff+older</td></tr>
708
- <tr><td>retry_duration</td><td></td><td>string</td><td></td><td></td><td></td><td>TODO</td><td>Specifies how long to wait before retrying transfer. (e.g. "5min")</td></tr>
709
- <tr><td>http_fallback</td><td></td><td>bool (node), integer</td><td></td><td></td><td></td><td>-y<br/>TODO</td><td>When true(1), attempts to perform an HTTP transfer if a fasp transfer cannot be performed.</td></tr>
710
- <tr><td>create_dir</td><td></td><td>boolean</td><td class="yes">Y</td><td class="yes">Y</td><td class="yes">Y</td><td>-d</td><td>Specifies whether to create new directories.</td></tr>
711
- <tr><td>precalculate_job_size</td><td>srv. def.</td><td>boolean</td><td class="yes">Y</td><td class="yes">Y</td><td class="yes">Y</td><td>--precalculate-job-size</td><td>Specifies whether to precalculate the job size.</td></tr>
712
- <tr><td>delete_source</td><td></td><td>boolean</td><td></td><td class="yes">Y</td><td></td><td>?</td><td>?</td></tr>
713
- <tr><td>remove_after_transfer</td><td></td><td>boolean</td><td></td><td class="yes">Y</td><td></td><td>?</td><td>Specifies whether to remove file after transfer.</td></tr>
714
- <tr><td>remove_empty_directories</td><td></td><td>boolean</td><td></td><td class="yes">Y</td><td></td><td>?</td><td>Specifies whether to remove empty directories.</td></tr>
715
- <tr><td>multi_session</td><td>1</td><td>integer</td><td class="no">N</td><td class="yes">Y</td><td class="no">N</td><td>-C</td><td>Specifies how many parts the transfer is in.</td></tr>
716
- <tr><td>multi_session_threshold</td><td>null</td><td>integer</td><td class="no">N</td><td class="yes">Y</td><td class="no">N</td><td>-</td><td>in bytes</td></tr>
717
- <tr><td>dgram_size</td><td></td><td>integer</td><td class="yes">Y</td><td></td><td></td><td>-Z</td><td>in bytes</td></tr>
718
- <tr><td>compression</td><td></td><td>integer</td><td></td><td></td><td></td><td></td><td>ascp4 only, 0 / 1?</td></tr>
719
- <tr><td>read_threads</td><td></td><td>integer</td><td></td><td></td><td></td><td>-</td><td>ascp4 only</td></tr>
720
- <tr><td>write_threads</td><td></td><td>integer</td><td></td><td></td><td></td><td>-</td><td>ascp4 only</td></tr>
721
- <tr><td>use_ascp4</td><td>false</td><td>boolean</td><td></td><td class="yes">Y</td><td></td><td>-</td><td>specify version of protocol</td></tr>
722
- <tr><td>paths</td><td>source files (dest)</td><td>array</td><td></td><td></td><td></td><td>positional<br/>--file-list<br/>--file-pair-list</td><td>Contains a path to the source (required) and a path to the destination.</td></tr>
723
- <tr><td>http_fallback_port</td><td></td><td>integer</td><td class="yes">Y</td><td></td><td></td><td>-t</td><td>Specifies http port.</td></tr>
724
- <tr><td>https_fallback_port</td><td></td><td>integer</td><td></td><td></td><td></td><td>todo</td><td>Specifies https port.</td></tr>
725
- <tr><td>cipher_allowed</td><td></td><td>string</td><td></td><td></td><td></td><td>-</td><td>returned by node API. Valid literals include "aes-128" and "none".</td></tr>
726
- <tr><td>target_rate_cap_kbps</td><td></td><td></td><td class="no">N</td><td class="no">?</td><td class="yes">?</td><td>-</td><td>Returned by upload/download_setup node api.</td></tr>
727
- <tr><td>rate_policy_allowed</td><td></td><td></td><td></td><td></td><td></td><td>-</td><td>returned by node API. Specifies most aggressive rate policy that is allowed. Valid literals include "low", "fair","high" and "fixed".</td></tr>
728
- <tr><td>ssh_private_key</td><td></td><td>string</td><td></td><td></td><td></td><td>-</td><td>todo</td></tr>
729
- <tr><td>remote_password</td><td>-</td><td>string</td><td class="yes">Y</td><td class="yes">Y</td><td class="yes">Y</td><td>PASS</td><td>SSH session password</td></tr>
730
- <tr><td>resume_policy</td><td>faspmgr:<br/>none<br/>other:<br/>sparse_csum</td><td>string</td><td class="yes">Y</td><td class="yes">Y</td><td class="yes">Y</td><td>-k</td><td>none,attrs,sparse_csum,full_csum</td></tr>
731
- <tr><td>authentication</td><td>faspmgr:<br/>none<br/>other:<br/>sparse_csum</td><td>string</td><td class="yes">Y</td><td class="yes">Y</td><td class="no">N</td><td>-</td><td>token: Aspera web keys are provided to allow transparent web based session initiation. on connect: password is not asked. Else, password is asked, and keys are not provided.</td></tr>
732
- <tr><td>EX_ssh_key_value</td><td>-</td><td>string</td><td class="yes">Y</td><td class="no">N</td><td class="no">N</td><td>KEY</td><td>Private key used for SSH authentication</td></tr>
733
- <tr><td>EX_ssh_key_paths</td><td>-</td><td>array</td><td class="yes">Y</td><td class="no">N</td><td class="no">N</td><td>-i</td><td>Use public key authentication and specify the private key file</td></tr>
734
- <tr><td>EX_at_rest_password</td><td>-</td><td>string</td><td class="yes">Y</td><td class="no">N</td><td class="no">N</td><td>FILEPASS</td><td>Passphrase used for at rest encryption or decryption</td></tr>
735
- <tr><td>EX_proxy_password</td><td>-</td><td>string</td><td class="yes">Y</td><td class="no">N</td><td class="no">N</td><td>PROXY_PASS</td><td>TODO</td></tr>
736
- <tr><td>EX_fasp_proxy_url</td><td>-</td><td>string</td><td class="yes">Y</td><td class="no">N</td><td class="no">N</td><td>--proxy</td><td>Specify the address of the Aspera high-speed proxy server</td></tr>
737
- <tr><td>EX_http_proxy_url</td><td>-</td><td>string</td><td class="yes">Y</td><td class="no">N</td><td class="no">N</td><td>-x</td><td>Specify the proxy server address used by HTTP Fallback</td></tr>
738
- <tr><td>EX_ascp_args</td><td>-</td><td>array</td><td class="yes">Y</td><td class="no">N</td><td class="no">N</td><td>same</td><td>Add command line arguments to ascp</td></tr>
739
- <tr><td>EX_http_transfer_jpeg</td><td>0</td><td>integer</td><td class="yes">Y</td><td class="no">N</td><td class="no">N</td><td>-j</td><td>HTTP transfers as JPEG file</td></tr>
740
- </table>
665
+ All standard _transfer-spec_ parameters can be overloaded. To display parameters,
666
+ run in debug mode (--log-level=debug). [_transfer-spec_](#transferspec) can
667
+ also be saved/overridden in the config file.
741
668
 
742
669
  ### Destination folder for transfers
743
670
 
744
- The destination folder is set by `aslmcli` by default to:
671
+ The destination folder is set by `mlia` by default to:
745
672
 
746
673
  * `.` for downloads
747
674
  * `/` for uploads
748
675
 
749
- It is specified by the [_transfer-spec_](#_transferspec_) parameter `destination_root`. As such, it can be modified with option: `--ts=@json:'{"destination_root":"<path>"}'`.
676
+ It is specified by the [_transfer-spec_](#transferspec) parameter `destination_root`. As such, it can be modified with option: `--ts=@json:'{"destination_root":"<path>"}'`.
750
677
  The option `to_folder` provides a convenient way to change this parameter: `--to-folder=<path>` and is equivalent.
751
678
 
752
679
  ### <a name="multisession"></a>Support of multi-session
@@ -770,7 +697,7 @@ Multi-session is directly supported by the node daemon.
770
697
  Note: resume policy of "attr" may cause problems. "none" or "sparse_csum"
771
698
  shall be preferred.
772
699
 
773
- Multi-session spawn is done by `aslmcli`.
700
+ Multi-session spawn is done by `mlia`.
774
701
 
775
702
 
776
703
  ### Examples
@@ -816,126 +743,126 @@ Usually the OS native scheduler shall already provide some sort of such protecti
816
743
  A non complete list of commands used in unit tests:
817
744
 
818
745
  ```bash
819
- aslmcli
820
- aslmcli --no-default node --url=my_url_here --username=my_username_here --password=my_password_here --insecure=yes delete /500M.dat
821
- aslmcli --no-default node --url=my_url_here --username=my_username_here --password=my_password_here --insecure=yes upload --to-folder=/ 500M.dat --ts=@json:'{"precalculate_job_size":true}' --transfer=node --transfer-node=@json:'{"url":"my_url_here","username":"my_username_here","password":"my_password_here"}'
822
- aslmcli --version)
823
- aslmcli -Pnode_lmdk08 --url=my_url_here --username=my_username_here node acc create --value=@json:'{"id":"aoc_1","secret":"_my_pass_","storage":{"type":"local","path":"/"}}'
824
- aslmcli -Pnode_lmdk08 --url=my_url_here --username=my_username_here node acc delete --id=aoc_1
825
- aslmcli -h
826
- aslmcli aspera admin ats access_key --id=testkey2 delete
827
- aslmcli aspera admin ats access_key --id=testkey2 node browse /
828
- aslmcli aspera admin ats access_key --id=testkey3 delete
829
- aslmcli aspera admin ats access_key create --cloud=aws --region=eu-west-1 --params=@json:'{"id":"testkey3","name":"laurent key AWS","storage":{"type":"aws_s3","bucket":"sedemo-ireland","credentials":{"access_key_id":"my_access_key_id_here","secret_access_key":"my_secret_access_key_here"},"path":"/laurent"}}'
830
- aslmcli aspera admin ats access_key create --cloud=softlayer --region=ams --params=@json:'{"id":"testkey2","name":"laurent key","storage":{"type":"softlayer_swift","container":"laurent","credentials":{"api_key":"my_api_key_here","username":"my_username_here"},"path":"/"}}'
831
- aslmcli aspera admin ats access_key list --fields=name,id,secret
832
- aslmcli aspera admin ats cluster clouds
833
- aslmcli aspera admin ats cluster list
834
- aslmcli aspera admin ats cluster show --cloud=aws --region=eu-west-1
835
- aslmcli aspera admin ats cluster show --id=1f412ae7-869a-445c-9c05-02ad16813be2
836
- aslmcli aspera admin events
837
- aslmcli aspera admin resource node --name=eudemo --secret=my_secret_here do access_key create --value=@json:'{"id":"testsub1","storage":{"path":"/folder1"}}'
838
- aslmcli aspera admin resource node --name=eudemo --secret=my_secret_here do access_key delete --eid=testsub1
839
- aslmcli aspera admin resource node --name=eudemo --secret=my_secret_here do delete /folder1
840
- aslmcli aspera admin resource node --name=eudemo --secret=my_secret_here do mkdir /folder1
841
- aslmcli aspera admin resource node --name=eudemo do browse / --secret=my_secret_here
842
- aslmcli aspera admin resource workspace list
843
- aslmcli aspera admin resource workspace_membership list --fields=ALL --query=@json:'{"page":1,"per_page":50,"embed":"member","inherited":false,"workspace_id":11363,"sort":"name"}'
844
- aslmcli aspera admin set_client_key ERuzXGuPA @file:$(APIKEY)
845
- aslmcli aspera files browse /
846
- aslmcli aspera files download /200KB.1 --to-folder=sample_dest_folder --download=node
847
- aslmcli aspera files download /200KB.1 --to-folder=sample_dest_folder --transfer=connect
848
- aslmcli aspera files upload sample_file.bin --to-folder=/
849
- aslmcli aspera packages list
850
- aslmcli aspera packages list --format=csv --fields=id|head -n 1)
851
- aslmcli aspera packages send sample_file.bin --note="my note" --title="my title" --recipient="laurent.martin.aspera@fr.ibm.com"
852
- aslmcli ats access_key --id=testkey2 cluster
853
- aslmcli ats access_key --id=testkey2 delete
854
- aslmcli ats access_key --id=testkey2 node browse /
855
- aslmcli ats access_key --id=testkey3 delete
856
- aslmcli ats access_key create --cloud=aws --region=eu-west-1 --params=@json:'{"id":"testkey3","name":"laurent key AWS","storage":{"type":"aws_s3","bucket":"sedemo-ireland","credentials":{"access_key_id":"my_access_key_id_here","secret_access_key":"my_secret_access_key_here"},"path":"/laurent"}}'
857
- aslmcli ats access_key create --cloud=softlayer --region=ams --params=@json:'{"id":"testkey2","name":"laurent key","storage":{"type":"softlayer_swift","container":"laurent","credentials":{"api_key":"my_api_key_here","username":"my_username_here"},"path":"/"}}'
858
- aslmcli ats access_key list --fields=name,id,secret
859
- aslmcli ats cluster clouds
860
- aslmcli ats cluster list
861
- aslmcli ats cluster show --cloud=aws --region=eu-west-1
862
- aslmcli ats cluster show --id=1f412ae7-869a-445c-9c05-02ad16813be2
863
- aslmcli ats credential cache list
864
- aslmcli ats credential info
865
- aslmcli ats credential list
866
- aslmcli ats credential subscriptions
867
- aslmcli client available
868
- aslmcli client connect id 'Aspera Connect for Windows' info
869
- aslmcli client connect id 'Aspera Connect for Windows' links id 'Windows Installer' download --to-folder=.
870
- aslmcli client connect id 'Aspera Connect for Windows' links list
871
- aslmcli client connect list
872
- aslmcli client current
873
- aslmcli config id conf_name delete
874
- aslmcli config id conf_name initialize @json:'{"p1":"v1","p2":"v2"}'
875
- aslmcli config id conf_name set param value
876
- aslmcli config id conf_name show
877
- aslmcli config id conf_name update --p1=v1 --p2=v2
878
- aslmcli config id default set shares conf_name
879
- aslmcli config list
880
- aslmcli config open
881
- aslmcli config overview
882
- aslmcli console transfer current list
883
- aslmcli erb README.erb.md > README.md
884
- aslmcli faspex package list
885
- aslmcli faspex package list --fields=delivery_id --format=csv --box=sent|tail -n 1) --box=sent
886
- aslmcli faspex package send --load-params=reset --url=my_url_here --username=my_username_here --password=my_password_here --insecure=yes --note="my note" --title="my title" --recipient="laurent.martin.aspera@fr.ibm.com" ~/200KB.1
887
- aslmcli faspex package send sample_file.bin --note="my note" --title="my title" --recipient="laurent.martin.aspera@fr.ibm.com"
888
- aslmcli faspex recv_publink 'https://faspex.mycompany.com/aspera/faspex/external_deliveries/78780?passcode=a003aaf2f53e3869126b908525084db6bebc7031' --insecure=yes
889
- aslmcli node async --id=1 counters
890
- aslmcli node async --id=1 summary
891
- aslmcli node async list
892
- aslmcli node browse / -r
893
- aslmcli node delete sample_dest_folder200KB.1
894
- aslmcli node download sample_dest_folder200KB.1 --to-folder=sample_dest_folder
895
- aslmcli node service --id=service1 delete
896
- aslmcli node service create @json:'{"id":"service1","type":"WATCHD","run_as":{"user":"user1"}}'
897
- aslmcli node service list
898
- aslmcli node transfer list
899
- aslmcli node upload sample_file.bin --to-folder=sample_dest_folder
900
- aslmcli orchestrator info
901
- aslmcli orchestrator plugins
902
- aslmcli orchestrator processes
903
- aslmcli orchestrator workflow --id=10 inputs
904
- aslmcli orchestrator workflow --id=10 start --params=@json:'{"Param":"laurent"}'
905
- aslmcli orchestrator workflow --id=10 start --params=@json:'{"Param":"laurent"}' --result=ResultStep:Complete_status_message
906
- aslmcli orchestrator workflow --id=10 status
907
- aslmcli orchestrator workflow list
908
- aslmcli orchestrator workflow status
909
- aslmcli preview events --skip-types=office
910
- aslmcli preview scan --skip-types=office --log-level=info
911
- aslmcli preview test ~/Documents/Samples/anatomic-2k/TG18-CH/TG18-CH-2k-01.dcm --log-level=debug png --video=clips
912
- aslmcli server browse /
913
- aslmcli server browse /Upload/target_hot
914
- aslmcli server cp /Upload/200KB.1 /Upload/200KB.2
915
- aslmcli server delete /Upload/200KB.1
916
- aslmcli server delete /Upload/target_hot
917
- aslmcli server delete /Upload/to.delete
918
- aslmcli server df
919
- aslmcli server download /Upload/200KB.1 --to-folder=sample_dest_folder
920
- aslmcli server du /
921
- aslmcli server info
922
- aslmcli server md5sum /Upload/200KB.1
923
- aslmcli server mkdir /Upload/123 --logger=stdout
924
- aslmcli server mkdir /Upload/target_hot
925
- aslmcli server mv /Upload/200KB.2 /Upload/to.delete
926
- aslmcli server rm /Upload/123
927
- aslmcli server upload sample_file.bin --to-folder=/Upload
928
- aslmcli server upload source_hot --to-folder=/Upload/target_hot --lock-port=12345 --ts=@json:'{"EX_ascp_args":["--remove-after-transfer","--remove-empty-directories","--exclude-newer-than=-8","--src-base","source_hot"]}'
929
- aslmcli shares repository browse /
930
- aslmcli shares repository delete /$(TEST_SHARE)/200KB.1
931
- aslmcli shares repository download /$(TEST_SHARE)/200KB.1 --to-folder=sample_dest_folder
932
- aslmcli shares repository upload sample_file.bin --to-folder=/$(TEST_SHARE)
933
- aslmcli shares2 appinfo
934
- aslmcli shares2 organization list
935
- aslmcli shares2 project list --organization=Sport
936
- aslmcli shares2 repository browse /
937
- aslmcli shares2 userinfo
938
- aslmcli sync start --parameters=@json:'{"sessions":[{"name":"test","reset":true,"remote_dir":"/sync_test","local_dir":"contents","host":"10.25.0.8","user":"user1","private_key_path":"/Users/laurent/.ssh/id_rsa"}]}'
746
+ mlia
747
+ mlia --no-default node --url=my_url_here --username=my_username_here --password=my_password_here --insecure=yes delete /500M.dat
748
+ mlia --no-default node --url=my_url_here --username=my_username_here --password=my_password_here --insecure=yes upload --to-folder=/ 500M.dat --ts=@json:'{"precalculate_job_size":true}' --transfer=node --transfer-node=@json:'{"url":"my_url_here","username":"my_username_here","password":"my_password_here"}'
749
+ mlia --version)
750
+ mlia --version` TOOLNAME=$(EXENAME) erb README.erb.md > README.md
751
+ mlia -Pnode_lmdk08 --url=my_url_here --username=my_username_here node acc create --value=@json:'{"id":"aoc_1","secret":"_my_pass_","storage":{"type":"local","path":"/"}}'
752
+ mlia -Pnode_lmdk08 --url=my_url_here --username=my_username_here node acc delete --id=aoc_1
753
+ mlia -h
754
+ mlia aspera admin ats access_key --id=testkey2 delete
755
+ mlia aspera admin ats access_key --id=testkey2 node browse /
756
+ mlia aspera admin ats access_key --id=testkey3 delete
757
+ mlia aspera admin ats access_key create --cloud=aws --region=eu-west-1 --params=@json:'{"id":"testkey3","name":"laurent key AWS","storage":{"type":"aws_s3","bucket":"sedemo-ireland","credentials":{"access_key_id":"my_access_key_id_here","secret_access_key":"my_secret_access_key_here"},"path":"/laurent"}}'
758
+ mlia aspera admin ats access_key create --cloud=softlayer --region=ams --params=@json:'{"id":"testkey2","name":"laurent key","storage":{"type":"softlayer_swift","container":"laurent","credentials":{"api_key":"my_api_key_here","username":"my_username_here"},"path":"/"}}'
759
+ mlia aspera admin ats access_key list --fields=name,id,secret
760
+ mlia aspera admin ats cluster clouds
761
+ mlia aspera admin ats cluster list
762
+ mlia aspera admin ats cluster show --cloud=aws --region=eu-west-1
763
+ mlia aspera admin ats cluster show --id=1f412ae7-869a-445c-9c05-02ad16813be2
764
+ mlia aspera admin events
765
+ mlia aspera admin resource node --name=eudemo --secret=my_secret_here do access_key create --value=@json:'{"id":"testsub1","storage":{"path":"/folder1"}}'
766
+ mlia aspera admin resource node --name=eudemo --secret=my_secret_here do access_key delete --eid=testsub1
767
+ mlia aspera admin resource node --name=eudemo --secret=my_secret_here do delete /folder1
768
+ mlia aspera admin resource node --name=eudemo --secret=my_secret_here do mkdir /folder1
769
+ mlia aspera admin resource node --name=eudemo do browse / --secret=my_secret_here
770
+ mlia aspera admin resource workspace list
771
+ mlia aspera admin resource workspace_membership list --fields=ALL --query=@json:'{"page":1,"per_page":50,"embed":"member","inherited":false,"workspace_id":11363,"sort":"name"}'
772
+ mlia aspera admin set_client_key ERuzXGuPA @file:$(APIKEY)
773
+ mlia aspera files browse /
774
+ mlia aspera files download /200KB.1 --to-folder=sample_dest_folder --download=node
775
+ mlia aspera files download /200KB.1 --to-folder=sample_dest_folder --transfer=connect
776
+ mlia aspera files upload sample_file.bin --to-folder=/
777
+ mlia aspera packages list
778
+ mlia aspera packages list --format=csv --fields=id|head -n 1)
779
+ mlia aspera packages send sample_file.bin --note="my note" --title="my title" --recipient="laurent.martin.aspera@fr.ibm.com"
780
+ mlia ats access_key --id=testkey2 cluster
781
+ mlia ats access_key --id=testkey2 delete
782
+ mlia ats access_key --id=testkey2 node browse /
783
+ mlia ats access_key --id=testkey3 delete
784
+ mlia ats access_key create --cloud=aws --region=eu-west-1 --params=@json:'{"id":"testkey3","name":"laurent key AWS","storage":{"type":"aws_s3","bucket":"sedemo-ireland","credentials":{"access_key_id":"my_access_key_id_here","secret_access_key":"my_secret_access_key_here"},"path":"/laurent"}}'
785
+ mlia ats access_key create --cloud=softlayer --region=ams --params=@json:'{"id":"testkey2","name":"laurent key","storage":{"type":"softlayer_swift","container":"laurent","credentials":{"api_key":"my_api_key_here","username":"my_username_here"},"path":"/"}}'
786
+ mlia ats access_key list --fields=name,id,secret
787
+ mlia ats cluster clouds
788
+ mlia ats cluster list
789
+ mlia ats cluster show --cloud=aws --region=eu-west-1
790
+ mlia ats cluster show --id=1f412ae7-869a-445c-9c05-02ad16813be2
791
+ mlia ats credential cache list
792
+ mlia ats credential info
793
+ mlia ats credential list
794
+ mlia ats credential subscriptions
795
+ mlia client available
796
+ mlia client connect id 'Aspera Connect for Windows' info
797
+ mlia client connect id 'Aspera Connect for Windows' links id 'Windows Installer' download --to-folder=.
798
+ mlia client connect id 'Aspera Connect for Windows' links list
799
+ mlia client connect list
800
+ mlia client current
801
+ mlia config id conf_name delete
802
+ mlia config id conf_name initialize @json:'{"p1":"v1","p2":"v2"}'
803
+ mlia config id conf_name set param value
804
+ mlia config id conf_name show
805
+ mlia config id conf_name update --p1=v1 --p2=v2
806
+ mlia config id default set shares conf_name
807
+ mlia config list
808
+ mlia config open
809
+ mlia config overview
810
+ mlia console transfer current list
811
+ mlia faspex package list
812
+ mlia faspex package list --fields=delivery_id --format=csv --box=sent|tail -n 1) --box=sent
813
+ mlia faspex package send --load-params=reset --url=my_url_here --username=my_username_here --password=my_password_here --insecure=yes --note="my note" --title="my title" --recipient="laurent.martin.aspera@fr.ibm.com" ~/200KB.1
814
+ mlia faspex package send sample_file.bin --note="my note" --title="my title" --recipient="laurent.martin.aspera@fr.ibm.com"
815
+ mlia faspex recv_publink 'https://faspex.mycompany.com/aspera/faspex/external_deliveries/78780?passcode=a003aaf2f53e3869126b908525084db6bebc7031' --insecure=yes
816
+ mlia node async --id=1 counters
817
+ mlia node async --id=1 summary
818
+ mlia node async list
819
+ mlia node browse / -r
820
+ mlia node delete sample_dest_folder200KB.1
821
+ mlia node download sample_dest_folder200KB.1 --to-folder=sample_dest_folder
822
+ mlia node service --id=service1 delete
823
+ mlia node service create @json:'{"id":"service1","type":"WATCHD","run_as":{"user":"user1"}}'
824
+ mlia node service list
825
+ mlia node transfer list
826
+ mlia node upload sample_file.bin --to-folder=sample_dest_folder
827
+ mlia orchestrator info
828
+ mlia orchestrator plugins
829
+ mlia orchestrator processes
830
+ mlia orchestrator workflow --id=10 inputs
831
+ mlia orchestrator workflow --id=10 start --params=@json:'{"Param":"laurent"}'
832
+ mlia orchestrator workflow --id=10 start --params=@json:'{"Param":"laurent"}' --result=ResultStep:Complete_status_message
833
+ mlia orchestrator workflow --id=10 status
834
+ mlia orchestrator workflow list
835
+ mlia orchestrator workflow status
836
+ mlia preview events --skip-types=office
837
+ mlia preview scan --skip-types=office --log-level=info
838
+ mlia preview test ~/Documents/Samples/anatomic-2k/TG18-CH/TG18-CH-2k-01.dcm --log-level=debug png --video=clips
839
+ mlia server browse /
840
+ mlia server browse /Upload/target_hot
841
+ mlia server cp /Upload/200KB.1 /Upload/200KB.2
842
+ mlia server delete /Upload/200KB.1
843
+ mlia server delete /Upload/target_hot
844
+ mlia server delete /Upload/to.delete
845
+ mlia server df
846
+ mlia server download /Upload/200KB.1 --to-folder=sample_dest_folder
847
+ mlia server du /
848
+ mlia server info
849
+ mlia server md5sum /Upload/200KB.1
850
+ mlia server mkdir /Upload/123 --logger=stdout
851
+ mlia server mkdir /Upload/target_hot
852
+ mlia server mv /Upload/200KB.2 /Upload/to.delete
853
+ mlia server rm /Upload/123
854
+ mlia server upload sample_file.bin --to-folder=/Upload
855
+ mlia server upload source_hot --to-folder=/Upload/target_hot --lock-port=12345 --ts=@json:'{"EX_ascp_args":["--remove-after-transfer","--remove-empty-directories","--exclude-newer-than=-8","--src-base","source_hot"]}'
856
+ mlia shares repository browse /
857
+ mlia shares repository delete /$(TEST_SHARE)/200KB.1
858
+ mlia shares repository download /$(TEST_SHARE)/200KB.1 --to-folder=sample_dest_folder
859
+ mlia shares repository upload sample_file.bin --to-folder=/$(TEST_SHARE)
860
+ mlia shares2 appinfo
861
+ mlia shares2 organization list
862
+ mlia shares2 project list --organization=Sport
863
+ mlia shares2 repository browse /
864
+ mlia shares2 userinfo
865
+ mlia sync start --parameters=@json:'{"sessions":[{"name":"test","reset":true,"remote_dir":"/sync_test","local_dir":"contents","host":"10.25.0.8","user":"user1","private_key_path":"/Users/laurent/.ssh/id_rsa"}]}'
939
866
 
940
867
  ...and more
941
868
  ```
@@ -943,18 +870,18 @@ aslmcli sync start --parameters=@json:'{"sessions":[{"name":"test","reset":true,
943
870
  ## <a name="usage"></a>Usage
944
871
 
945
872
  ```bash
946
- $ aslmcli -h
873
+ $ mlia -h
947
874
  NAME
948
- aslmcli -- a command line tool for Aspera Applications (v0.8.10)
875
+ mlia -- a command line tool for Aspera Applications (v0.9)
949
876
 
950
877
  SYNOPSIS
951
- aslmcli COMMANDS [OPTIONS] [ARGS]
878
+ mlia COMMANDS [OPTIONS] [ARGS]
952
879
 
953
880
  DESCRIPTION
954
881
  Use Aspera application to perform operations on command line.
955
882
  OAuth 2.0 is used for authentication in Files, Several authentication methods are provided.
956
883
  Documentation and examples: https://rubygems.org/gems/asperalm
957
- execute: aslmcli conf doc
884
+ execute: mlia conf doc
958
885
 
959
886
  COMMANDS
960
887
  First level commands: config
@@ -969,17 +896,17 @@ ARGS
969
896
  Some commands require mandatory arguments, e.g. a path.
970
897
 
971
898
  OPTIONS: global
972
- --interactive=ENUM use interactive input of missing params: yes, no
899
+ --interactive=ENUM use interactive input of missing params: yes, no
973
900
  --ask-options=ENUM ask even optional options: yes, no
974
901
  --table-style=VALUE table display style, current=:.:
975
902
  -h, --help Show this message.
976
903
  --show-config Display parameters used for the provided action.
977
904
  -r, --rest-debug more debug for HTTP calls
978
905
  -v, --version display version
979
- --config-file=VALUE read parameters from file in YAML format, current=/Users/laurent/.aspera/aslmcli/config.yaml
906
+ --config-file=VALUE read parameters from file in YAML format, current=/Users/laurent/.aspera/mlia/config.yaml
980
907
  -N, --no-default do not load default configuration for plugin
981
908
  --ui=ENUM method to start browser: text, graphical
982
- --log-level=ENUM Log level: error, fatal, unknown, debug, info, warn
909
+ --log-level=ENUM Log level: info, warn, error, fatal, unknown, debug
983
910
  --logger=ENUM log method: stderr, stdout, syslog
984
911
  --format=ENUM output format: table, ruby, json, jsonpp, yaml, csv
985
912
  -P, --presetVALUE load the named option preset from current config file
@@ -1001,7 +928,7 @@ OPTIONS: global
1001
928
  COMMAND: config
1002
929
  SUBCOMMANDS: todo
1003
930
  OPTIONS:
1004
- --config-file=VALUE read parameters from file in YAML format, current=/Users/laurent/.aspera/aslmcli/config.yaml
931
+ --config-file=VALUE read parameters from file in YAML format, current=/Users/laurent/.aspera/mlia/config.yaml
1005
932
  -N, --no-default do not load default configuration for plugin
1006
933
 
1007
934
  COMMAND: shares
@@ -1176,7 +1103,7 @@ Note that actions and parameter values can be written in short form.
1176
1103
 
1177
1104
  # Application Plugins
1178
1105
 
1179
- `aslmcli` comes with several Aspera application plugins.
1106
+ `mlia` comes with several Aspera application plugins.
1180
1107
 
1181
1108
  ## General: Application URL and Authentication
1182
1109
 
@@ -1199,10 +1126,10 @@ This requires additional setup.
1199
1126
 
1200
1127
  ### Configuration Wizard
1201
1128
 
1202
- `aslmcli` provides a configuration wizard, to invoke it do:
1129
+ `mlia` provides a configuration wizard, to invoke it do:
1203
1130
 
1204
1131
  ```
1205
- $ aslmcli config wizard aspera --url=https://sedemo.ibmaspera.com
1132
+ $ mlia config wizard aspera --url=https://sedemo.ibmaspera.com
1206
1133
  ```
1207
1134
 
1208
1135
  If the `url` parameter is not provided it will be asked on command line.
@@ -1223,11 +1150,11 @@ For a _quick start_, follow the mandatory and sufficient section: [API Client Re
1223
1150
 
1224
1151
  For a more convenient, browser-less, experience follow the [JWT](#jwt) section (auth=jwt) in addition to Client Registration.
1225
1152
 
1226
- In Oauth, a "Bearer" token are generated to authenticate REST calls. Bearer tokens are valid for a period of time.`aslmcli` saves generated tokens in its configuration folder, tries to re-use them or regenerates them when they have expired.
1153
+ In Oauth, a "Bearer" token are generated to authenticate REST calls. Bearer tokens are valid for a period of time.`mlia` saves generated tokens in its configuration folder, tries to re-use them or regenerates them when they have expired.
1227
1154
 
1228
1155
  ### <a name="clientreg"></a>API Client Registration
1229
1156
 
1230
- The first step is to declare `aslmcli` in Aspera on Cloud using the admin interface.
1157
+ The first step is to declare `mlia` in Aspera on Cloud using the admin interface.
1231
1158
 
1232
1159
  (official documentation: [https://aspera.asperafiles.com/helpcenter/admin/organization/registering-an-api-client](https://aspera.asperafiles.com/helpcenter/admin/organization/registering-an-api-client) ).
1233
1160
 
@@ -1238,14 +1165,14 @@ Let's start by a registration with web based authentication (auth=web):
1238
1165
  * Open a web browser, log to your instance: e.g. `https://laurent.ibmaspera.com/`
1239
1166
  * Go to Admin View-Organization-API Clients-Create
1240
1167
  * Fill the API client creation form:
1241
- * Client Name: `aslmcli`
1168
+ * Client Name: `mlia`
1242
1169
  * Redirect URIs: `http://localhost:12345`
1243
1170
  * Origins: `localhost`
1244
1171
  * uncheck "Prompt users to allow client to access"
1245
1172
  * leave JWT unchecked for now
1246
1173
  * Submit
1247
1174
 
1248
- Note: for web based authentication, `aslmcli` listens on a local port (e.g. by default 12345), and the browser will provide the OAuth code there. For ``aslmcli` http is required, and 12345 is the default port.
1175
+ Note: for web based authentication, `mlia` listens on a local port (e.g. by default 12345), and the browser will provide the OAuth code there. For ``mlia` http is required, and 12345 is the default port.
1249
1176
 
1250
1177
  <img src="docs/Auth-registered-client.png" alt="Screenshot:Registered API Client"/>
1251
1178
 
@@ -1253,10 +1180,10 @@ Once the client is registered, a "Client ID" and "Secret" are created, these val
1253
1180
 
1254
1181
  ### <a name="aocpreset"></a>Option Preset for Aspera on Cloud
1255
1182
 
1256
- It is convenient to save several of those parameters in an option preset for `aslmcli` in its configuration file. Lets create an option preset called: `my_aoc_org` using `ask` interactive input (client info from previous step):
1183
+ It is convenient to save several of those parameters in an option preset for `mlia` in its configuration file. Lets create an option preset called: `my_aoc_org` using `ask` interactive input (client info from previous step):
1257
1184
 
1258
1185
  ```
1259
- $ aslmcli config id my_aoc_org ask url client_id client_secret
1186
+ $ mlia config id my_aoc_org ask url client_id client_secret
1260
1187
  option: url> https://laurent.ibmaspera.com/
1261
1188
  option: client_id> BJLPObQiFw
1262
1189
  option: client_secret> yFS1mu-crbKuQhGFtfhYuoRW...
@@ -1268,17 +1195,17 @@ updated: my_aoc_org
1268
1195
  Define this preset as default configuration for the `aspera` plugin:
1269
1196
 
1270
1197
  ```bash
1271
- $ aslmcli config id default set aspera my_aoc_org
1198
+ $ mlia config id default set aspera my_aoc_org
1272
1199
  ```
1273
1200
 
1274
1201
  Note: Default `auth` method is `web` and default `redirect_uri` is `http://localhost:12345`.
1275
1202
 
1276
1203
  ### <a name="aocfirst"></a>First Use
1277
1204
 
1278
- Once client has been registered and option preset created: `aslmcli` can be used:
1205
+ Once client has been registered and option preset created: `mlia` can be used:
1279
1206
 
1280
1207
  ```bash
1281
- $ aslmcli aspera files br /
1208
+ $ mlia aspera files br /
1282
1209
  Current Workspace: Default Workspace (default)
1283
1210
  empty
1284
1211
  ```
@@ -1302,13 +1229,13 @@ This can be done using any of the following method:
1302
1229
  * using the CLI:
1303
1230
 
1304
1231
  ```bash
1305
- $ aslmcli config genkey ~/.aspera/aslmcli/aocapikey
1232
+ $ mlia config genkey ~/.aspera/$ mlia/aocapikey
1306
1233
  ```
1307
1234
 
1308
1235
  * `ssh-keygen`:
1309
1236
 
1310
1237
  ```bash
1311
- $ ssh-keygen -t rsa -f ~/.aspera/aslmcli/aocapikey -N ''
1238
+ $ ssh-keygen -t rsa -f ~/.aspera/$ mlia/aocapikey -N ''
1312
1239
  ```
1313
1240
 
1314
1241
  * `openssl`
@@ -1316,7 +1243,7 @@ $ ssh-keygen -t rsa -f ~/.aspera/aslmcli/aocapikey -N ''
1316
1243
  (on some openssl implementation (mac) there is option: -nodes (no DES))
1317
1244
 
1318
1245
  ```bash
1319
- $ APIKEY=~/.aspera/aslmcli/aocapikey
1246
+ $ APIKEY=~/.aspera/$ mlia/aocapikey
1320
1247
  $ openssl genrsa -passout pass:dummypassword -out ${APIKEY}.protected 2048
1321
1248
  $ openssl rsa -passin pass:dummypassword -in ${APIKEY}.protected -out ${APIKEY}
1322
1249
  $ openssl rsa -pubout -in ${APIKEY} -out ${APIKEY}.pub
@@ -1346,13 +1273,13 @@ Note: It is also possible to allow a "super key" to impersonate any user by regi
1346
1273
  ##### Using command line
1347
1274
 
1348
1275
  ```bash
1349
- $ aslmcli aspera admin res client list
1276
+ $ mlia aspera admin res client list
1350
1277
  :............:.........:
1351
1278
  : id : name :
1352
1279
  :............:.........:
1353
- : BJLPObQiFw : aslmcli :
1280
+ : BJLPObQiFw : $ mlia :
1354
1281
  :............:.........:
1355
- $ aslmcli aspera admin res client --id=BJLPObQiFw modify @json:'{"jwt_grant_enabled":true,"explicit_authorization_required":false}'
1282
+ $ mlia aspera admin res client --id=BJLPObQiFw modify @json:'{"jwt_grant_enabled":true,"explicit_authorization_required":false}'
1356
1283
  modified
1357
1284
  ```
1358
1285
 
@@ -1373,14 +1300,14 @@ The public key must be assigned to your user. This can be done in two manners:
1373
1300
  ##### Using command line
1374
1301
 
1375
1302
  ```bash
1376
- $ aslmcli aspera admin res user list
1303
+ $ mlia aspera admin res user list
1377
1304
  :........:................:
1378
1305
  : id : name :
1379
1306
  :........:................:
1380
1307
  : 109952 : Tech Support :
1381
1308
  : 109951 : LAURENT MARTIN :
1382
1309
  :........:................:
1383
- $ aslmcli aspera admin res user --id=109951 modify @ruby:'{"public_key"=>File.read(File.expand_path("~/.aspera/aslmcli/aocapikey.pub"))}'
1310
+ $ mlia aspera admin res user --id=109951 modify @ruby:'{"public_key"=>File.read(File.expand_path("~/.aspera/$ mlia/aocapikey.pub"))}'
1384
1311
  modified
1385
1312
  ```
1386
1313
 
@@ -1388,7 +1315,7 @@ Note: the `show` command can be used to verify modifications.
1388
1315
 
1389
1316
  #### Preset modification for JWT
1390
1317
 
1391
- To activate JWT authentication for `aslmcli` using the preset, do the folowing:
1318
+ To activate JWT authentication for `mlia` using the preset, do the folowing:
1392
1319
 
1393
1320
  * change auth method to JWT
1394
1321
  * provide location of private key
@@ -1397,7 +1324,7 @@ To activate JWT authentication for `aslmcli` using the preset, do the folowing:
1397
1324
  Execute:
1398
1325
 
1399
1326
  ```bash
1400
- $ aslmcli config id my_aoc_org update --auth=jwt --private-key=@val:@file:~/.aspera/aslmcli/aocapikey --username=laurent.martin.aspera@fr.ibm.com
1327
+ $ mlia config id my_aoc_org update --auth=jwt --private-key=@val:@file:~/.aspera/$ mlia/aocapikey --username=laurent.martin.aspera@fr.ibm.com
1401
1328
  ```
1402
1329
 
1403
1330
  Note: the private key argument represents the actual PEM string. In order to read the content from a file, use the @file: prefix. But if the @file: argument is used as is, it will read the file and set in the config file. So to keep the "@file" tag in the configuration file, the @val: prefix is added.
@@ -1432,7 +1359,7 @@ Refer to the AoC API for full list of query parameters.
1432
1359
  * Bulk creation
1433
1360
 
1434
1361
  ```bash
1435
- $ aslmcli aspera admin res user create --bulk=yes @json:'[{"email":"dummyuser1@example.com"},{"email":"dummyuser2@example.com"}]'
1362
+ $ mlia aspera admin res user create --bulk=yes @json:'[{"email":"dummyuser1@example.com"},{"email":"dummyuser2@example.com"}]'
1436
1363
  :.......:.........:
1437
1364
  : id : status :
1438
1365
  :.......:.........:
@@ -1444,17 +1371,17 @@ $ aslmcli aspera admin res user create --bulk=yes @json:'[{"email":"dummyuser1@e
1444
1371
  * Find with filter and delete
1445
1372
 
1446
1373
  ```bash
1447
- $ aslmcli aspera admin res user list --query='@json:{"q":"dummyuser"}' --fields=id,email
1374
+ $ mlia aspera admin res user list --query='@json:{"q":"dummyuser"}' --fields=id,email
1448
1375
  :.......:........................:
1449
1376
  : id : email :
1450
1377
  :.......:........................:
1451
1378
  : 98398 : dummyuser1@example.com :
1452
1379
  : 98399 : dummyuser2@example.com :
1453
1380
  :.......:........................:
1454
- $ thelist=$(echo $(aslmcli aspera admin res user list --query='@json:{"q":"dummyuser"}' --fields=id,email --field=id --format=csv)|tr ' ' ,)
1381
+ $ thelist=$(echo $($ mlia aspera admin res user list --query='@json:{"q":"dummyuser"}' --fields=id,email --field=id --format=csv)|tr ' ' ,)
1455
1382
  $ echo $thelist
1456
1383
  98398,98399
1457
- $ aslmcli aspera admin res user --bulk=yes --id=@json:[$thelist] delete
1384
+ $ mlia aspera admin res user --bulk=yes --id=@json:[$thelist] delete
1458
1385
  :.......:.........:
1459
1386
  : id : status :
1460
1387
  :.......:.........:
@@ -1466,7 +1393,7 @@ $ aslmcli aspera admin res user --bulk=yes --id=@json:[$thelist] delete
1466
1393
  * Display current users workspaces
1467
1394
 
1468
1395
  ```
1469
- $ aslmcli aspera user workspaces
1396
+ $ mlia aspera user workspaces
1470
1397
  :......:............................:
1471
1398
  : id : name :
1472
1399
  :......:............................:
@@ -1481,13 +1408,13 @@ $ aslmcli aspera user workspaces
1481
1408
  Creation of a sub-access key is like creation of access key with the following difference: authentication to node API is made with accesskey (master access key) and only the path parameter is provided: it is relative to the storage root of the master key. (id and secret are optional)
1482
1409
 
1483
1410
  ```
1484
- $ aslmcli aspera admin resource node --name=_node_name_ --secret=_secret_ do access_key create --value=@json:'{"storage":{"path":"/folder1"}}'
1411
+ $ mlia aspera admin resource node --name=_node_name_ --secret=_secret_ do access_key create --value=@json:'{"storage":{"path":"/folder1"}}'
1485
1412
  ```
1486
1413
 
1487
1414
  * display members of a workspace
1488
1415
 
1489
1416
  ```
1490
- $ aslmcli aspera admin res workspace_membership list --fields=member_type,manager,member.email --query=@json:'{"page":1,"per_page":50,"embed":"member","inherited":false,"workspace_id":11363,"sort":"name"}'
1417
+ $ mlia aspera admin res workspace_membership list --fields=member_type,manager,member.email --query=@json:'{"page":1,"per_page":50,"embed":"member","inherited":false,"workspace_id":11363,"sort":"name"}'
1491
1418
  :.............:.........:..................................:
1492
1419
  : member_type : manager : member.email :
1493
1420
  :.............:.........:..................................:
@@ -1515,7 +1442,7 @@ The central subcommand uses the "reliable query" API (session and file). It allo
1515
1442
 
1516
1443
  Filtering can be applied:
1517
1444
  ```
1518
- $ aslmcli node central file list
1445
+ $ mlia node central file list
1519
1446
  ```
1520
1447
 
1521
1448
  by providing the `validator` option, offline transfer validation can be done.
@@ -1524,26 +1451,26 @@ by providing the `validator` option, offline transfer validation can be done.
1524
1451
 
1525
1452
  It is possible to start a FASPStream session using the node API:
1526
1453
 
1527
- Use the "node stream create" command, then arguments are provided as a [_transfer-spec_](#_transferspec_).
1454
+ Use the "node stream create" command, then arguments are provided as a [_transfer-spec_](#transferspec).
1528
1455
 
1529
1456
  ```bash
1530
- ./bin/aslmcli node stream create --ts=@json:'{"direction":"send","source":"udp://233.3.3.4:3000?loopback=1&ttl=2","destination":"udp://233.3.3.3:3001/","remote_host":"localhost","remote_user":"stream","remote_password":"XXXX"}' --load-params=stream
1457
+ ./bin/$ mlia node stream create --ts=@json:'{"direction":"send","source":"udp://233.3.3.4:3000?loopback=1&ttl=2","destination":"udp://233.3.3.3:3001/","remote_host":"localhost","remote_user":"stream","remote_password":"XXXX"}' --load-params=stream
1531
1458
  ```
1532
1459
 
1533
1460
  ### Watchfolder
1534
1461
 
1535
1462
  Refer to [Aspera documentation](https://download.asperasoft.com/download/docs/entsrv/3.7.4/es_admin_linux/webhelp/index.html#watchfolder_external/dita/json_conf.html) for watch folder creation.
1536
1463
 
1537
- `aslmcli` supports remote operations through the node API. Operations are:
1464
+ `mlia` supports remote operations through the node API. Operations are:
1538
1465
 
1539
1466
  * Start watchd and watchfolderd services running as a system user having access to files
1540
1467
  * configure a watchfolder to define automated transfers
1541
1468
 
1542
1469
 
1543
1470
  ```bash
1544
- $ aslmcli node service create @json:'{"id":"mywatchd","type":"WATCHD","run_as":{"user":"user1"}}'
1545
- $ aslmcli node service create @json:'{"id":"mywatchfolderd","type":"WATCHFOLDERD","run_as":{"user":"user1"}}'
1546
- $ aslmcli node watch_folder create @json:'{"id":"mywfolder","source_dir":"/watch1","target_dir":"/","transport":{"host":"10.25.0.4","user":"user1","pass":"mypassword"}}'
1471
+ $ mlia node service create @json:'{"id":"mywatchd","type":"WATCHD","run_as":{"user":"user1"}}'
1472
+ $ mlia node service create @json:'{"id":"mywatchfolderd","type":"WATCHFOLDERD","run_as":{"user":"user1"}}'
1473
+ $ mlia node watch_folder create @json:'{"id":"mywfolder","source_dir":"/watch1","target_dir":"/","transport":{"host":"10.25.0.4","user":"user1","pass":"mypassword"}}'
1547
1474
  ```
1548
1475
 
1549
1476
  ### Out of Transfer File Validation
@@ -1551,13 +1478,13 @@ $ aslmcli node watch_folder create @json:'{"id":"mywfolder","source_dir":"/watch
1551
1478
  Follow the Aspera Transfer Server configuration to activate this feature.
1552
1479
 
1553
1480
  ```
1554
- $ aslmcli node central file list --validator=aslmcli --data=@json:'{"file_transfer_filter":{"max_result":1}}'
1481
+ $ mlia node central file list --validator=$ mlia --data=@json:'{"file_transfer_filter":{"max_result":1}}'
1555
1482
  :..............:..............:............:......................................:
1556
1483
  : session_uuid : file_id : status : path :
1557
1484
  :..............:..............:............:......................................:
1558
1485
  : 1a74444c-... : 084fb181-... : validating : /home/xfer.../PKG - my title/200KB.1 :
1559
1486
  :..............:..............:............:......................................:
1560
- $ aslmcli node central file update --validator=aslmcli --data=@json:'{"files":[{"session_uuid": "1a74444c-...","file_id": "084fb181-...","status": "completed"}]}'
1487
+ $ mlia node central file update --validator=$ mlia --data=@json:'{"files":[{"session_uuid": "1a74444c-...","file_id": "084fb181-...","status": "completed"}]}'
1561
1488
  updated
1562
1489
  ```
1563
1490
 
@@ -1573,7 +1500,7 @@ Create another configuration for the Azure ATS instance: in section "node", name
1573
1500
  Then execute the following command:
1574
1501
 
1575
1502
  ```bash
1576
- $ aslmcli node download /share/sourcefile --to-folder=/destinationfolder --load-params=awsshod --transfer=node --transfer-node=@param:azureats
1503
+ $ mlia node download /share/sourcefile --to-folder=/destinationfolder --load-params=awsshod --transfer=node --transfer-node=@param:azureats
1577
1504
  ```
1578
1505
 
1579
1506
  This will get transfer information from the SHOD instance and tell the Azure ATS instance
@@ -1582,7 +1509,7 @@ to download files.
1582
1509
  ### Create access key
1583
1510
 
1584
1511
  ```
1585
- $ aslmcli node access_key create --value=@json:'{"id":"eudemo-sedemo","secret":"mystrongsecret","storage":{"type":"local","path":"/data/asperafiles"}}'
1512
+ $ mlia node access_key create --value=@json:'{"id":"eudemo-sedemo","secret":"mystrongsecret","storage":{"type":"local","path":"/data/asperafiles"}}'
1586
1513
  ```
1587
1514
 
1588
1515
  ## <a name="client"></a>Client
@@ -1598,7 +1525,7 @@ The `client` plugin refers to the use of a local FASP client. It provides the fo
1598
1525
  Locally installed Aspera products can be listed with:
1599
1526
 
1600
1527
  ```bash
1601
- $ aslmcli client available
1528
+ $ mlia client available
1602
1529
  :..........................:................................................:
1603
1530
  : name : app_root :
1604
1531
  :..........................:................................................:
@@ -1614,11 +1541,11 @@ To select another product use option: `use_product`, either on command line:
1614
1541
  `--use-product='Aspera Enterprise Server'`, or by setting as default:
1615
1542
 
1616
1543
  ```
1617
- $ aslmcli config id cli_default set use_product 'Aspera Enterprise Server'
1544
+ $ mlia config id cli_default set use_product 'Aspera Enterprise Server'
1618
1545
  updated: cli_default: use_product <- Aspera Enterprise Server
1619
- $ aslmcli config id default set config cli_default
1546
+ $ mlia config id default set config cli_default
1620
1547
  updated: default: config <- cli_default
1621
- $ aslmcli client current
1548
+ $ mlia client current
1622
1549
  :........................:.......................................................................................:
1623
1550
  : name : path :
1624
1551
  :........................:.......................................................................................:
@@ -1638,7 +1565,7 @@ $ aslmcli client current
1638
1565
  ### List current resources used
1639
1566
 
1640
1567
  ```
1641
- $ aslmcli client current
1568
+ $ mlia client current
1642
1569
  :........................:............................................................................................:
1643
1570
  : name : path :
1644
1571
  :........................:............................................................................................:
@@ -1657,7 +1584,7 @@ $ aslmcli client current
1657
1584
  ### Installation of Connect Client on command line
1658
1585
 
1659
1586
  ```bash
1660
- $ ./bin/aslmcli client connect list
1587
+ $ ./bin/$ mlia client connect list
1661
1588
  :...............................................:......................................:..............:
1662
1589
  : id : title : version :
1663
1590
  :...............................................:......................................:..............:
@@ -1670,7 +1597,7 @@ $ ./bin/aslmcli client connect list
1670
1597
  : urn:uuid:213C9370-22B1-11E2-81C1-0800200C9A66 : Aspera Connect for Linux 32 : 3.6.2.117442 :
1671
1598
  : urn:uuid:97F94DF0-22B1-11E2-81C1-0800200C9A66 : Aspera Connect for Linux 64 : 3.7.2.141527 :
1672
1599
  :...............................................:......................................:..............:
1673
- $ aslmcli client connect id 'Aspera Connect for Mac Intel 10.6' links list
1600
+ $ mlia client connect id 'Aspera Connect for Mac Intel 10.6' links list
1674
1601
  :.............................................:..........................:.......................................................................:..........:...............:
1675
1602
  : title : type : href : hreflang : rel :
1676
1603
  :.............................................:..........................:.......................................................................:..........:...............:
@@ -1683,7 +1610,7 @@ $ aslmcli client connect id 'Aspera Connect for Mac Intel 10.6' links list
1683
1610
  : Aspera Connect PDF Documentation for Mac OS : application/pdf : docs/user/osx/zh-cn/pdf/Connect_User_3.7.0_OSX_zh-cn.pdf : zh-cn : documentation :
1684
1611
  : Aspera Connect for Mac Release Notes : text/html : http://www.asperasoft.com/en/release_notes/default_1/release_notes_54 : en : release-notes :
1685
1612
  :.............................................:..........................:.......................................................................:..........:...............:
1686
- $ aslmcli client connect id 'Aspera Connect for Mac Intel 10.6' links id 'Mac Intel Installer' download --to-folder=.
1613
+ $ mlia client connect id 'Aspera Connect for Mac Intel 10.6' links id 'Mac Intel Installer' download --to-folder=.
1687
1614
  downloaded: AsperaConnect-3.6.1.111259-mac-intel-10.6.dmg
1688
1615
  ```
1689
1616
 
@@ -1696,10 +1623,10 @@ Works at FASP level (SSH/ascp/ascmd). (different from node api)
1696
1623
  One can test the "server" application using the well known demo server:
1697
1624
 
1698
1625
  ```bash
1699
- $ aslmcli config id aspera_demo_server update --url=ssh://demo.asperasoft.com:33001 --username=asperaweb --password=demoaspera
1700
- $ aslmcli config id default set server aspera_demo_server
1701
- $ aslmcli server browse /aspera-test-dir-large
1702
- $ aslmcli server download /aspera-test-dir-large/200MB
1626
+ $ mlia config id aspera_demo_server update --url=ssh://demo.asperasoft.com:33001 --username=asperaweb --password=demoaspera
1627
+ $ mlia config id default set server aspera_demo_server
1628
+ $ mlia server browse /aspera-test-dir-large
1629
+ $ mlia server download /aspera-test-dir-large/200MB
1703
1630
  ```
1704
1631
 
1705
1632
  This creates a option preset "aspera_demo_server" and set it as default for application "server"
@@ -1759,40 +1686,40 @@ and here: [https://developer.asperasoft.com/web/node/access-keys](https://develo
1759
1686
  Example: create access key on softlayer:
1760
1687
 
1761
1688
  ```
1762
- aslmcli ats access_key create --cloud=softlayer --region=ams --params=@json:'{"storage":{"type":"softlayer_swift","container":"_container_name_","credentials":{"api_key":"value","username":"_name_:_usr_name_"},"path":"/"},"id":"_optional_id_","name":"_optional_name_"}'
1689
+ $ mlia ats access_key create --cloud=softlayer --region=ams --params=@json:'{"storage":{"type":"softlayer_swift","container":"_container_name_","credentials":{"api_key":"value","username":"_name_:_usr_name_"},"path":"/"},"id":"_optional_id_","name":"_optional_name_"}'
1763
1690
  ```
1764
1691
 
1765
1692
  Example: create access key on AWS:
1766
1693
 
1767
1694
  ```
1768
- aslmcli ats access_key create --cloud=aws --region=eu-west-1 --params=@json:'{"id":"testkey3","name":"laurent key AWS","storage":{"type":"aws_s3","bucket":"my-bucket","credentials":{"access_key_id":"AKIA_MY_API_KEY","secret_access_key":"my/secret/here"},"path":"/laurent"}}'
1695
+ $ mlia ats access_key create --cloud=aws --region=eu-west-1 --params=@json:'{"id":"testkey3","name":"laurent key AWS","storage":{"type":"aws_s3","bucket":"my-bucket","credentials":{"access_key_id":"AKIA_MY_API_KEY","secret_access_key":"my/secret/here"},"path":"/laurent"}}'
1769
1696
 
1770
1697
  ```
1771
1698
 
1772
1699
  Example: create access key on Azure SAS:
1773
1700
 
1774
1701
  ```
1775
- aslmcli ats access_key create --cloud=azure --region=eastus --params=@json:'{"id":"testkeyazure","name":"laurent key azure","storage":{"type":"azure_sas","credentials":{"shared_access_signature":"https://xxxx.blob.core.windows.net/..."},"path":"/"}}'
1702
+ $ mlia ats access_key create --cloud=azure --region=eastus --params=@json:'{"id":"testkeyazure","name":"laurent key azure","storage":{"type":"azure_sas","credentials":{"shared_access_signature":"https://xxxx.blob.core.windows.net/..."},"path":"/"}}'
1776
1703
 
1777
1704
  ```
1778
1705
 
1779
1706
  Example: create access key on Azure:
1780
1707
 
1781
1708
  ```
1782
- aslmcli ats access_key create --cloud=azure --region=eastus --params=@json:'{"id":"testkeyazure","name":"laurent key azure","storage":{"type":"azure","credentials":{"account":"myaccount","key":"myaccesskey","storage_endpoint":"myblob"},"path":"/"}}'
1709
+ $ mlia ats access_key create --cloud=azure --region=eastus --params=@json:'{"id":"testkeyazure","name":"laurent key azure","storage":{"type":"azure","credentials":{"account":"myaccount","key":"myaccesskey","storage_endpoint":"myblob"},"path":"/"}}'
1783
1710
 
1784
1711
  ```
1785
1712
 
1786
1713
  delete all my access keys:
1787
1714
 
1788
1715
  ```
1789
- for k in $(aslmcli ats access_key list --field=id --format=csv);do aslmcli ats access_key id $k delete;done
1716
+ for k in $($ mlia ats access_key list --field=id --format=csv);do $ mlia ats access_key id $k delete;done
1790
1717
  ```
1791
1718
 
1792
1719
  ## IBM Aspera Sync
1793
1720
 
1794
- A basic plugin to start an "async" using aslmcli. The main advantage is the possibility
1795
- to start from ma configuration file, using aslmcli standard options.
1721
+ A basic plugin to start an "async" using $ mlia. The main advantage is the possibility
1722
+ to start from ma configuration file, using $ mlia standard options.
1796
1723
 
1797
1724
  ## Preview
1798
1725
 
@@ -1819,16 +1746,16 @@ This is related to:
1819
1746
 
1820
1747
  ### Configuration
1821
1748
 
1822
- Like any aslmcli commands, parameters can be passed on command line or using a configuration option preset. Example using a option preset:
1749
+ Like any $ mlia commands, parameters can be passed on command line or using a configuration option preset. Example using a option preset:
1823
1750
 
1824
1751
  ```
1825
- $ aslmcli config id my_aoc_access_key update --url=https://localhost:9092 --username=my_access_key --password=my_secret
1826
- $ aslmcli config id default set preview my_aoc_access_key
1752
+ $ mlia config id my_aoc_access_key update --url=https://localhost:9092 --username=my_access_key --password=my_secret
1753
+ $ mlia config id default set preview my_aoc_access_key
1827
1754
  ```
1828
1755
 
1829
1756
  Once can check if the access key is well configured using:
1830
1757
  ```
1831
- $ aslmcli -Pmy_aoc_access_key node browse /
1758
+ $ mlia -Pmy_aoc_access_key node browse /
1832
1759
  ```
1833
1760
 
1834
1761
  ### Execution
@@ -1873,7 +1800,7 @@ If the preview generator does not have access to files on the file system (it is
1873
1800
  To skip some folders, use the option : `--skip-folders`, note that it expects a list of path starting with slash, use the `@json:` notation, example:
1874
1801
 
1875
1802
  ```
1876
- $ aslmcli preview scan --skip-folders=@json:'["/not_here"]'
1803
+ $ mlia preview scan --skip-folders=@json:'["/not_here"]'
1877
1804
  ```
1878
1805
 
1879
1806
  ### Examples
@@ -1881,14 +1808,14 @@ $ aslmcli preview scan --skip-folders=@json:'["/not_here"]'
1881
1808
  on command line:
1882
1809
 
1883
1810
  ```bash
1884
- aslmcli preview event --skip-types=office --file-access=remote --overwrite=always --iteration-file=/tmp/restart.txt --lock-port=12346
1811
+ $ mlia preview event --skip-types=office --file-access=remote --overwrite=always --iteration-file=/tmp/restart.txt --lock-port=12346
1885
1812
  ```
1886
1813
 
1887
1814
  with crontab:
1888
1815
 
1889
1816
  ```bash
1890
- 2-59 * * * * su -s /bin/bash - xfer -c 'timeout 10m aslmcli preview event --skip-types=office --lock-port=12346 --log-level=info --logger=syslog --iteration-file=/tmp/preview_restart.txt'
1891
- 0 * * * * su -s /bin/bash - xfer -c 'timeout 30m aslmcli preview scan --skip-types=office --lock-port=12346 --log-level=info --logger=syslog'
1817
+ 2-59 * * * * su -s /bin/bash - xfer -c 'timeout 10m $ mlia preview event --skip-types=office --lock-port=12346 --log-level=info --logger=syslog --iteration-file=/tmp/preview_restart.txt'
1818
+ 0 * * * * su -s /bin/bash - xfer -c 'timeout 30m $ mlia preview scan --skip-types=office --lock-port=12346 --log-level=info --logger=syslog'
1892
1819
  ```
1893
1820
 
1894
1821
  ### External tools: Linux
@@ -1948,7 +1875,7 @@ service xvfb start
1948
1875
  This gem comes with a second executable tool providing a simplified standardized interface
1949
1876
  to start a FASP session: ```asession```.
1950
1877
 
1951
- It aims at simplifying the startup of a FASP session from a programmatic stand point as formating a [_transfer-spec_](#_transferspec_) is:
1878
+ It aims at simplifying the startup of a FASP session from a programmatic stand point as formating a [_transfer-spec_](#transferspec) is:
1952
1879
 
1953
1880
  * common to Aspera Node API (HTTP POST /ops/transfer)
1954
1881
  * common to Aspera Connect API (browser javascript startTransfer)
@@ -1956,9 +1883,9 @@ It aims at simplifying the startup of a FASP session from a programmatic stand p
1956
1883
 
1957
1884
  This makes it easy to integrate with any language provided that one can spawn a sub process, write to its STDIN, read from STDOUT, generate and parse JSON.
1958
1885
 
1959
- The tool expect one single argument: a [_transfer-spec_](#_transferspec_).
1886
+ The tool expect one single argument: a [_transfer-spec_](#transferspec).
1960
1887
 
1961
- If not argument is provided, it assumes a value of: `@json:@stdin`, i.e. a JSON formated [_transfer-spec_](#_transferspec_) on stdin.
1888
+ If not argument is provided, it assumes a value of: `@json:@stdin`, i.e. a JSON formated [_transfer-spec_](#transferspec) on stdin.
1962
1889
 
1963
1890
  Note that if JSON is the format, one has to specify `@json:` to tell the tool to decode the hash using JSON.
1964
1891
 
@@ -2030,7 +1957,7 @@ EXAMPLES
2030
1957
 
2031
1958
  ## Requirements
2032
1959
 
2033
- `aslmcli` maybe used as a simple hot folder engine. A hot folder being defined as a tool that:
1960
+ `mlia` maybe used as a simple hot folder engine. A hot folder being defined as a tool that:
2034
1961
 
2035
1962
  * locally (or remotely) detects new files in a top folder
2036
1963
  * send detected files to a remote (respectively, local) repository
@@ -2045,7 +1972,7 @@ In addition: the detection should be made "continuously" or on specific time/dat
2045
1972
  The general idea is to rely on :
2046
1973
 
2047
1974
  * existing `ascp` features for detection and transfer
2048
- * take advantage of `aslmcli` configuration capabilities and server side knowledge
1975
+ * take advantage of `mlia` configuration capabilities and server side knowledge
2049
1976
  * the OS scheduler for reliability and continuous operation
2050
1977
 
2051
1978
  ### ascp features
@@ -2059,7 +1986,7 @@ Interesting ascp features are found in its arguments: (see ascp manual):
2059
1986
 
2060
1987
  Note that:
2061
1988
 
2062
- * aslmcli takes transfer parameters exclusively as a transfer_spec, with `--ts` parameter.
1989
+ * $ mlia takes transfer parameters exclusively as a transfer_spec, with `--ts` parameter.
2063
1990
  * not all native ascp arguments are available as standard transfer_spec parameters
2064
1991
  * native ascp arguments can be provided with the transfer spec parameter: EX_ascp_args (array), only for the "local" transfer agent (not connect or node)
2065
1992
 
@@ -2071,12 +1998,12 @@ Note: parameters may be saved in a preset and used with `-P`.
2071
1998
 
2072
1999
  ### Scheduling
2073
2000
 
2074
- Once aslmcli parameters are defined, run the command using the OS native scheduler, e.g. every minutes, or 5 minutes, etc... Refer to section [_Scheduling_](#_scheduling_).
2001
+ Once $ mlia parameters are defined, run the command using the OS native scheduler, e.g. every minutes, or 5 minutes, etc... Refer to section [_Scheduling_](#_scheduling_).
2075
2002
 
2076
2003
  ## Example
2077
2004
 
2078
2005
  ```
2079
- aslmcli server upload source_hot --to-folder=/Upload/target_hot --lock-port=12345 --ts=@json:'{"EX_ascp_args":["--remove-after-transfer","--remove-empty-directories","--exclude-newer-than=-8","--src-base","source_hot"]}'
2006
+ $ mlia server upload source_hot --to-folder=/Upload/target_hot --lock-port=12345 --ts=@json:'{"EX_ascp_args":["--remove-after-transfer","--remove-empty-directories","--exclude-newer-than=-8","--src-base","source_hot"]}'
2080
2007
 
2081
2008
  ```
2082
2009
 
@@ -2088,7 +2015,7 @@ Main components:
2088
2015
 
2089
2016
  * `Asperalm` generic classes for REST and OAuth
2090
2017
  * `Asperalm::Fasp`: starting and monitoring transfers. It can be considered as a FASPManager class for Ruby.
2091
- * `Asperalm::Cli`: the `aslmcli` tool.
2018
+ * `Asperalm::Cli`: `mlia`.
2092
2019
 
2093
2020
 
2094
2021
  # History
@@ -2100,11 +2027,11 @@ There were a few pitfalls:
2100
2027
  * The tool was written in the aging `perl` language while most Aspera application products (but the Transfer Server) are written in `ruby`.
2101
2028
  * The tool was only for transfers, but not able to call other products APIs
2102
2029
 
2103
- So, it evolved into `aslmcli`:
2030
+ So, it evolved into `mlia`:
2104
2031
 
2105
2032
  * portable: works on platforms supporting `ruby` (and `ascp`)
2106
2033
  * easy to install with the `gem` utility
2107
- * supports transfers with multiple [Transfer Agents](#agents), that&apos;s why transfer parameters moved from ascp command line to [_transfer-spec_](#_transferspec_) (more reliable , more standard)
2034
+ * supports transfers with multiple [Transfer Agents](#agents), that&apos;s why transfer parameters moved from ascp command line to [_transfer-spec_](#transferspec) (more reliable , more standard)
2108
2035
  * `ruby` is consistent with other Aspera products
2109
2036
 
2110
2037
 
@@ -2124,6 +2051,11 @@ This means that you do not have ruby support for ED25519 SSH keys. You may eithe
2124
2051
  Gems, or remove your ed25519 key from your `.ssh` folder to solve the issue.
2125
2052
 
2126
2053
  # Release Notes
2054
+ * version 0.9
2055
+
2056
+ * Renamed the CLI from aslmcli to $ mlia ("Amelia", Multi-Layer IBM Aspera command line interface)
2057
+ * Automatic rename and conversion of former config folder from aslmcli to $ mlia
2058
+
2127
2059
  * version 0.7.6
2128
2060
 
2129
2061
  * add "sync" plugin
@@ -2143,7 +2075,7 @@ Breaking change:
2143
2075
  * ats server list provisioned -> ats cluster list
2144
2076
  * ats server list clouds -> ats cluster clouds
2145
2077
  * ats server list instance --cloud=x --region=y -> ats cluster show --cloud=x --region=y
2146
- * ats server id xxx -> aslmcli ats cluster show --id=xxx
2078
+ * ats server id xxx -> $ mlia ats cluster show --id=xxx
2147
2079
  * ats subscriptions -> ats credential subscriptions
2148
2080
  * ats api_key repository list -> ats credential cache list
2149
2081
  * ats api_key list -> ats credential list