aspera-cli 4.25.3 → 4.26.0.pre

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d01aecb4590218d1028c4d4653c255394294cca477508cd802cf53b72acee927
-  data.tar.gz: 0ecb307d12fcc0daaa6d465928533d5fc95ac3f66218cc5b6c552d7e044aa822
+  metadata.gz: fc6adc843448ed8b76da0786b419be39fe4531daa0da0254f8cdb7503a131f4f
+  data.tar.gz: 217a266117e6a2ac2f0512016d71a7fa4e9a1b67924e3e73ca5b7a29cc54a76a
 SHA512:
-  metadata.gz: 01ba11f7c24c0f9f869770c9035edd0e2d7d06b77fb71ca00a16cf59829e6abaf758fe5c9a0e131019e6a11e09a58b1c1e9fb4cc9a7818bcda63fdf3ef8e8969
-  data.tar.gz: a70ffa0f67294841bb18a53720c656c2eea4d904cf0c14db259203cf75aa05090a2c64b040807d1d5bfd7eb7288969feb1756adc97415bc3b142cf3b55d2d48d
+  metadata.gz: 8977f967425a7a53c585d64902619366c197b6897231515ec84dd1b76e4a70eb767da6ce5cbe32f0f3005e70d222e1dc5d65fcf3bfe2c8044d4cf7349396e692
+  data.tar.gz: 7ac9b790563f1f8d11c1156f337ed4fb81313c64b11e1dc7b85909b91c87f06d0a6024176352a01c51397626d75ec20a66c9311dd8a5f88042cff7b0a23fdc44

data/CHANGELOG.md

@@ -2,6 +2,39 @@
 
 <!-- markdownlint-configure-file { "no-duplicate-heading": { "siblings_only": true } } -->
 
+## 4.26.0.pre
+
+Released: [Place date of release here]
+
+### New Features
+
+* `faspex5`: When sending a package, recipients specified in fields `private_recipients`, `notified_on_upload`, `notified_on_download` and `notified_on_receipt` are now also expanded like field `recipients`.
+
+### Issues Fixed
+
+* `sync`: #251 in `admin` command: Fixed database path on Windows: Use `~private-asp` instead of `.private-asp`.
+* `config`: Fixed `preset update` with dot-path options.
+
+### Breaking Changes
+
+## 4.25.4
+
+Released: 2026-03-04
+
+### New Features
+
+* **general**: If `@:` is used, then marker `END` optionally marks the end of collected arguments.
+* `format`: `display` defaults to `info` only if `format` is set to `table`, else defaults to `data`.
+* `node`: Parameter `accept_v4` of option `node_api` (boolean, defaults to `true`) allows using gen4 browsing with `Accept-Version: 4.0` for best performance when there are thousands of files.
+
+### Issues Fixed
+
+* `faspex5`: Listing content, or receiving a package requires API parameter: `recipient_user_id` or `recipient_workgroup_id`, else error `Not authorized` is returned.
+
+### Breaking Changes
+
+* `node`: Options `node_cache` and `default_ports` are replaced with option: `node_api` (`Hash`) with boolean parameters (keys): `cache` and `standard_ports` with default value `true`.
+
 ## 4.25.3
 
 Released: 2026-02-18
@@ -283,7 +316,7 @@ Released: 2025-01-21
 
 * Internal: Basic REST calls now return data directly. (no more `data` key). For advanced calls, use `call`.
 * Internal: Transfer SDK download is now a 2-step procedure: First get the YAML file from GitHub with URLs for the various platforms and versions, and then download the archive from the official IBM repository.
-**global**: Option `format=multi` is replaced with option `multi_table=yes`.
+* **global**: Option `format=multi` is replaced with option `multi_table=yes`.
 * `faspex5`: Removed deprecated option `value` replaced with positional parameter.
   
 ## 4.19.0
@@ -1047,7 +1080,7 @@ Released: 2021-02-03
 
 ### New Features
 
-* The option `value` of command `find`, to filter on name, is not optional.
+* The option `value` of command `find` to filter on name is mandatory.
 * `find` now also reports all types (file, folder, link).
 * `find` now is able to report all fields (type, size, etc...).
 
@@ -1077,7 +1110,7 @@ Released: 2021-02-03
 ### New Features
 
 * Improved wizard (prepare for AoC global client id).
-* Preview generator: Added option : --skip-format=&lt;png,mp4&gt;.
+* Preview generator: Added option : `skip_format` with values `png`, `mp4`.
 * Removed outdated pictures from this doc.
 
 ## 0.9.19
@@ -1145,7 +1178,7 @@ Released: 2021-02-03
 
 ### New Features
 
-* `faspex`: Use option `once_only` set to `yes` to enable cargo like function. id=NEW deprecated.
+* `faspex`: Use option `once_only` set to `yes` to enable cargo like function. `id=NEW` deprecated.
 * `aoc`: Share to share transfer with command `transfer`.
 
 ## 0.9.7
@@ -1154,8 +1187,8 @@ Released: 2021-02-03
 
 * Homogeneous transfer spec for `node` and [`direct`](README.md#agt_direct) transfer agents.
 * Preview persistency goes to unique file by default.
-* Catch mxf extension in preview as video.
-* Faspex: Possibility to download all packages by specifying id=ALL.
+* Catch `mxf` extension in preview as video.
+* Faspex: Possibility to download all packages by specifying `id=ALL`.
 * Faspex: To come: Cargo-like function to download only new packages with id=NEW.
 
 ## 0.9.6

data/CONTRIBUTING.md

@@ -2,24 +2,25 @@
 
 ## Reporting Issues and Vulnerabilities
 
-If you encounter a problem or a security vulnerability, please report it on [GitHub Issues](https://github.com/IBM/aspera-cli/issues).
+If you encounter a bug or a security vulnerability, please report it via [GitHub Issues](https://github.com/IBM/aspera-cli/issues).
 
-Before submitting a new issue:
+Before submitting a new report:
 
-- Search existing issues to see if your problem has already been reported or resolved.
+- **Search existing issues** to determine if the problem has already been documented or resolved.
 
-To help us assist you efficiently, include the following in your report:
+To help us diagnose and resolve the issue efficiently, please include the following in your report:
 
-- The version of `ascli` you are using:
+- The `ascli` version you are using:
 
-  ```bash
-  ascli version
+  ```shell
+  ascli -v
   ```
 
-- Confirmation that you are using the latest version (update it if needed).
-- Your Ruby version information:
+- **Update confirmation**: Verify that you are running the latest version.
 
-  ```bash
+- **Your Ruby environment details**:
+
+  ```shell
   ruby -v
   ```
 
@@ -29,103 +30,102 @@ We welcome contributions to improve the `aspera-cli` project!
 
 ### Getting Started
 
-Clone the repository and navigate to the project's root directory:
+Clone the repository to initialize the development environment:
 
-```bash
+```shell
 git clone https://github.com/IBM/aspera-cli.git
 cd aspera-cli
 bundle install
 bundle exec rake -T
 ```
 
-For testing instructions, refer to [Running Tests](#running-tests).
+For detailed testing instructions, please refer to [Running Tests](#running-tests).
 
 ### How to Contribute
 
-To submit a contribution:
+To submit a contribution, follow these steps:
 
 1. **Fork** the repository on GitHub.
 
-1. **Create a feature branch** for your changes.
+1. **Create a feature branch** specifically for your changes.
 
 1. **Implement** your feature or bug fix.
 
 1. **Write tests** to ensure your changes are robust and prevent regressions.
 
-1. Run `rubocop` to ensure your code follows the Ruby style guide.
+1. **Run** `rubocop` to ensure your code adheres to the Ruby style guide.
 
-1. Update `CHANGELOG.md` with a summary of your changes.
+1. **Update** `CHANGELOG.md` with a concise summary of your changes.
 
-1. Submit a **pull request** with a clear description of your contribution.
+1. **Submit a pull request** with a detailed description of your work.
 
 > [!TIP]
-> Make sure your pull request is focused and includes only relevant changes.
+> Keep pull requests focused; include only changes relevant to the specific feature or fix.
 
 ## Architecture
 
-The overall architecture of `aspera-cli` is modular and extensible.
+The `aspera-cli` architecture is designed to be modular and extensible.
 
 ![Architecture](docs/architecture.png)
 
 ### Structure Highlights
 
-- Entry Point:
+- **Entry Point**:
 
-  `lib/aspera/cli/main.rb`, CLI startup logic.
+  `lib/aspera/cli/main.rb` contains the core CLI startup logic.
 
-- Plugins:
+- **Plugins**:
 
-  Located in `lib/aspera/cli/plugins`; plugins extend CLI functionality and encapsulate specific features.
+  Located in `lib/aspera/cli/plugins`, these extend CLI functionality and encapsulate specific features.
 
-- Transfer Agents:
+- **Transfer Agents**:
 
-  Found in `lib/aspera/agent`, these handle data transfer operations.
+  Located in `lib/aspera/agent`, these components manage data transfer operations.
 
-Class diagrams are provided in <docs/uml.png>
+Detailed class diagrams are available in <docs/uml.png>
 
 ## Ruby Environment
 
-`aspera-cli` is written in Ruby.
-You can install Ruby using any method you prefer (e.g., `rbenv`, `rvm`, system package manager).
+`aspera-cli` is built with Ruby.
+You can manage your Ruby installation using your preferred tool (e.g., `rbenv`, `rvm`, or a system package manager).
 
 To start with a clean state and remove all installed gems:
 
-```bash
+```shell
 bundle exec rake tools:clean_gems
 ```
 
 > [!TIP]
-> This is especially useful before testing across different Ruby versions or preparing for a release.
+> This is particularly useful when testing across different Ruby versions or preparing for a new release.
 
 ## Toolchain
 
-The build system uses Ruby's `rake`.
+The build system is powered by Ruby's `rake`.
 
-### Environment
+### Environment Configuration
 
-A few macros and environment variables control certain aspects of the build:
+The following environment variables and macros control specific build behaviors:
 
-| Environment variable        | Description                                         |
-|-----------------------------|-----------------------------------------------------|
-| `ASPERA_CLI_TEST_CONF_URL`  | URL for configuration file with secrets for tests.  |
-| `ASPERA_CLI_DOC_CHECK_LINKS`| Check links still exist during doc generation.      |
-| `LOG_LEVEL`                 | Change log level in `rake` tasks.                   |
-| `LOG_SECRETS`               | Change log secrets in `rake` tasks.                   |
-| `ENABLE_COVERAGE`           | Enable test coverage analysis when set.             |
-| `SIGNING_KEY`               | Path to the signing key used to build the gem file. |
-| `SIGNING_KEY_PEM`           | PEM of signing key.                                 |
+| Environment variable        | Contents   | Description                                                  |
+|-----------------------------|------------| -------------------------------------------------------------|
+| `ASPERA_CLI_TEST_CONF_URL`  | URL        | URL for the configuration file containing secrets for tests. |
+| `ASPERA_CLI_DOC_CHECK_LINKS`| `yes`/`no` | Validates that links exist during documentation generation.  |
+| `LOG_SECRETS`               | `yes`/`no` | Toggles the logging of secrets in `rake` tasks.              |
+| `LOG_LEVEL`                 | `debug`, ... | Sets the logging verbosity for `rake` tasks.                 |
+| `ENABLE_COVERAGE`           | set/unset  | Enables test coverage analysis when defined.                 |
+| `SIGNING_KEY`               | File path  | Path to the signing key used for building the gem file.      |
+| `SIGNING_KEY_PEM`           | PEM Value  | The PEM content of the signing key.                          |
 
-These can be set either as environment variables or directly on the `rake` command line.
+These values can be set as standard environment variables or passed directly to the `rake` command.
 
-Setting `SIGNING_KEY_PEM` creates file `$HOME/.gem/signing_key.pem` and sets `SIGNING_KEY` to that path.
+Setting `SIGNING_KEY_PEM` automatically generates a file at `$HOME/.gem/signing_key.pem` and sets the `SIGNING_KEY` variable accordingly.
 
 > [!NOTE]
-> Environment variables `ASPERA_CLI_*` are typically set in the user’s shell profile for development.
-> Others are intended for use on the command line.
+> `ASPERA_CLI_TEST_CONF_URL` is typically defined in your shell profile for development, while others are usually for ad-hoc command-line use.
 
-To use the CLI directly from the development environment, add this to your shell profile (adapt the real path):
+To run the CLI directly from your source directory, add the following to your shell profile (adjust the path as necessary):
 
-```bash
+```shell
 dev_ascli=$HOME/github/aspera-cli
 export PATH=$dev_ascli/bin:$PATH
 export RUBYLIB=$dev_ascli/lib:$RUBYLIB
@@ -135,83 +135,83 @@ export RUBYLIB=$dev_ascli/lib:$RUBYLIB
 
 Documentation is generated with `pandoc` and `LaTeX`.
 
-The IBM `Plex` font is used; for installation instructions, see [IBM Plex](https://www.ibm.com/plex/).
+The project utilizes the **IBM Plex font**.
+Installation instructions can be found at [IBM Plex](https://www.ibm.com/plex/).
 
-On macOS, to install `lualatex` and all packages:
+On macOS, install `lualatex` and required packages via Homebrew:
 
-```bash
+```shell
 brew install texlive
 ```
 
-If `lualatex` is installed using another method, ensure that the following packages are installed:
+If using an alternative installation method, ensure the following packages are present:
 
-```bash
+```shell
 tlmgr update --self
 tlmgr install fvextra selnolig lualatex-math
 ```
 
-To check URLs during documentation generation, set the environment variable: `ASPERA_CLI_DOC_CHECK_LINKS=1`.
+- Validate URLs during generation: `ASPERA_CLI_DOC_CHECK_LINKS=yes`.
 
-To debug documentation generation, set the environment variable: `ASPERA_CLI_DOC_DEBUG=debug`.
+- Debug the generation process: `ASPERA_CLI_DOC_DEBUG=debug`.
 
-To generate documentation:
+- Build the documentation:
 
-```bash
+```shell
 rake doc:build
 ```
 
 ## Test Environment
 
-Refer to <tests/README.md>.
+Detailed testing information can be found in <tests/README.md>.
 
 ## Build
 
-The unsigned gem is built with:
+To build an unsigned gem:
 
-```bash
+```shell
 bundle install
 bundle exec rake unsigned
 ```
 
-If you don't want to install optional gems:
+To exclude optional gems from the installation:
 
-```bash
+```shell
 bundle config set without optional
 ```
 
 ### Signed gem
 
-A private key is required to generate a signed gem.
-Its path must be set using environment variable `SIGNING_KEY`.
-The gem is signed with the public certificate found in `certs` and the private key specified by `SIGNING_KEY` (kept secret by the maintainer).
+Generating a signed gem requires a **private key**, specified via the `SIGNING_KEY` environment variable.
+The gem is signed using the public certificate in `certs` and the **private key**.
 
-```bash
+```shell
 bundle exec rake SIGNING_KEY=/path/to/vault/gem-private_key.pem
 ```
 
-Refer to <certs/README.md>.
+For more details, see <certs/README.md>.
 
-### gRPC stubs for transfer SDK
+### gRPC stubs for Transfer SDK
 
-Update with:
+To update the stubs:
 
-```bash
+```shell
 bundle exec rake tools:grpc
 ```
 
-It downloads the latest `proto` file and then compiles it into ruby sources included in the repo.
+This task downloads the latest `.proto` files and compiles them into the Ruby source files included in the repository.
 
 ## Container image build
 
-See [Container build](./container/README.md).
+Refer to the [Container build guide](./container/README.md).
 
 ## Single executable build
 
-See [Executable build](build/binary/README.md).
+Refer to the [Executable build guide](build/binary/README.md).
 
-To list operations:
+To list related `rake` tasks:
 
-```bash
+```shell
 bundle exec rake -T ^binary:
 ```
 
@@ -219,87 +219,95 @@ bundle exec rake -T ^binary:
 
 ### Branching Strategy
 
-This project uses a single `main` branch for development.
-During the development cycle, the version in `lib/aspera/cli/version.rb` uses a `.pre` suffix (e.g., `x.y.z.pre`) to indicate a pre-release state.
+This project maintains a single `main` branch.
+During development, the version in `lib/aspera/cli/version.rb` includes a `.pre` suffix (e.g., `x.y.z.pre`).
+
+Contributions are handled as follows:
 
-Feature development and bug fixes can be done either:
+- **Direct commits** to `main`: Permitted for minor changes.
 
-- Directly on `main` for small changes
-- Via feature branches with pull requests for larger changes
+- **Feature branches**: Required for significant changes via pull requests.
 
-### Checklist Before a New Release
+### Pre-Release Checklist
 
-When preparing for a new release, do the following:
+Before a new release, ensure the following:
 
-- Run the test suite:
+- **Pass all tests**:
 
-```bash
+```shell
 bundle exec rake test:run
 ```
 
-- Verify that the container builds successfully (using the local gem file):
+- **Verify container builds** (using the local gem):
 
-```bash
+```shell
 bundle exec rake container:build'[local]'
 bundle exec rake container:test
 ```
 
+- **Check documentation links**:
+
+```shell
+bundle exec rake doc:build ASPERA_CLI_DOC_CHECK_LINKS=yes
+```
+
 ### Automated Release Process
 
-Releases are triggered via the GitHub Actions UI using the **Release** workflow (`.github/workflows/release.yml`).
+Releases are managed through the GitHub Actions UI via the **New Release on GitHub** workflow (`.github/workflows/release.yml`).
+
+1. Navigate to **Actions** > **New Release on GitHub**
+2. Select **Run workflow**
+3. (Optionally) Specify:
+   - **Release version**: Defaults to the current `version.rb` value (minus the `.pre` suffix).
 
-To create a release:
+     e.g. current `a.b.c.pre` &rarr; `a.b.c`.
+   - **Next development version**: Defaults to an incremented minor version with the `.pre` suffix.
 
-1. Navigate to **Actions** > **Release** in the GitHub repository
-2. Click **Run workflow**
-3. Optionally specify:
-   - **Release version**: The version to release. If left empty, uses the current version from `version.rb` without the `.pre` suffix.
-   - **Next development version**: The next version to prepare for. If left empty, auto-increments the minor version. The `.pre` suffix is added automatically.
+     e.g. release `a.b.c` &rarr; `a.(b+1).0.pre`.
 4. Click **Run workflow**
 
-The workflow automatically:
+The automated workflow performs the following:
 
-1. Updates `version.rb` with the release version
-2. Rebuilds documentation (PDF manual, Markdown README)
+1. Updates `version.rb` to the release version
+2. Rebuilds all documentation (PDF and Markdown)
 3. Commits the changes
 4. Creates and pushes the release tag
 5. Triggers the `deploy` workflow to publish to [rubygems.org](https://rubygems.org/gems/aspera-cli)
-6. Updates `version.rb` to the next development version with `.pre` suffix
-7. Commits and pushes the version bump in main branch.
+6. Increments `version.rb` to the next development version.
+7. Commits and pushes the version bump to `main`.
 
 ### Manual Release Process (Alternative)
 
-If needed, releases can still be done manually.
-Basically, follow the same procedure as in the GitHub action:
+If necessary, you can mirror the automated process manually:
 
 - Update the version in `lib/aspera/cli/version.rb` (remove `.pre` suffix)
 
-- Build the PDF manual in `pkg`:
+- Build the PDF manual:
 
 ```shell
 bundle exec rake doc:build
 ```
 
-- Build the signed `.gem` in `pkg`:
+- Build the signed gem:
 
 ```shell
 bundle exec rake SIGNING_KEY=/path/to/vault/gem-private_key.pem
 ```
 
-- Create the release version tag and push it to GitHub:
+- Tag the release and push to GitHub:
 
 ```shell
 bundle exec rake release_tag
 ```
 
-This will trigger the action `.github/workflows/deploy.yml`, which builds the gem file and pushes it to RubyGems.
+This triggers the `.github/workflows/deploy.yml` action to publish to RubyGems.
 
-- After release, update `version.rb` to the next development version with `.pre` suffix
+- Update `version.rb` to the next `.pre` development version.
 
 ## Future Improvements
 
-- Replace custom REST and OAuth classes with standard Ruby gems ?
-  - <https://github.com/rest-client/rest-client>
-  - <https://github.com/oauth-xx/oauth2>
-- Use the `thor` gem <http://whatisthor.com/> (or other standard Ruby CLI manager)
-- Look at <https://github.com/phusion/traveling-ruby>
+- Evaluate replacing custom REST and OAuth implementations with standard gems:
+  - [rest-client](https://github.com/rest-client/rest-client)
+  - [oauth2](https://github.com/oauth-xx/oauth2)
+- Integrate `thor` <http://whatisthor.com/> or another standard Ruby CLI framework.
+- Explore [Traveling Ruby](https://github.com/phusion/traveling-ruby) for distribution.

data/README.md

@@ -5,6 +5,8 @@
 [![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/5861/badge)](https://bestpractices.coreinfrastructure.org/projects/5861)
 [![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](LICENSE)
 
+![Hootput the Owl](docs/mascot.svg)
+
 **`ascli`** is the command-line interface for IBM Aspera products.
 Use it from the terminal or in scripts to:
 
@@ -18,8 +20,8 @@ Choose what best suits you:
 
 | Resource | Link |
 | -------- | ---- |
-| **Online manual** | [docs/README.md](docs/README.md) |
-| **PDF manual** | In [releases](https://github.com/IBM/aspera-cli/releases) |
+| **Online manual** | [GitHub docs/README.md](https://github.com/IBM/aspera-cli/blob/main/docs/README.md) |
+| **PDF manual** | In [GitHub Releases](https://github.com/IBM/aspera-cli/releases) |
 | **RubyGems** | [rubygems.org/gems/aspera-cli](https://rubygems.org/gems/aspera-cli) |
 | **RubyDoc** | [rubydoc.info/gems/aspera-cli](https://www.rubydoc.info/gems/aspera-cli) |
 | **Docsify** | [online](https://docsify-this.net/?basePath=https://raw.githubusercontent.com/IBM/aspera-cli/main/docs&homepage=README.md&sidebar=true&browser-tab-title=Aspera%20CLI%20Manual&hide-credits=true&maxLevel=4&externalLinkTarget=_blank&image-captions=true&dark-mode=auto) |
@@ -34,7 +36,7 @@ ascli config transferd install
 ```
 
 The second command installs the **FASP** transfer engine (`ascp`).
-For other install methods (single executable, Docker, Chocolatey, Homebrew), see the [user manual](docs/README.md#installation).
+For other install methods (single executable, Docker, Chocolatey, Homebrew), see the [user manual](https://github.com/IBM/aspera-cli/blob/main/docs/README.md#installation).
 
 **Quick check:**
 
@@ -44,13 +46,13 @@ ascli -v
 
 ## Contributing
 
-- **Bugs & features:** [BUGS.md](BUGS.md)
-- **How to contribute:** [CONTRIBUTING.md](CONTRIBUTING.md)
-- **Release notes:** [CHANGELOG.md](CHANGELOG.md)
+- **Bugs & features:** [BUGS.md](https://github.com/IBM/aspera-cli/blob/main/BUGS.md)
+- **How to contribute:** [CONTRIBUTING.md](https://github.com/IBM/aspera-cli/blob/main/CONTRIBUTING.md)
+- **Release notes:** [CHANGELOG.md](https://github.com/IBM/aspera-cli/blob/main/CHANGELOG.md)
 
 Commands map to Aspera REST APIs; see the manual for options.
 For debugging, use `--log-level=debug`.
 
 ## License
 
-[Apache-2.0](LICENSE)
+[Apache-2.0](https://github.com/IBM/aspera-cli/blob/main/LICENSE)

data/lib/aspera/agent/direct.rb

@@ -25,25 +25,27 @@ module Aspera
       private_constant :LISTEN_LOCAL_ADDRESS, :SELECT_AVAILABLE_PORT
 
       # Options: same as values in option `transfer_info`
-      # @param ascp_args         [Array]   (Params) Optional Additional arguments to ascp
-      # @param wss               [Boolean] (Params) `true`: if both SSH and wss in ts: prefer wss
-      # @param quiet             [Boolean] (Params) By default no native `ascp` progress bar
-      # @param monitor           [Boolean] (Params) Set to `false` to eliminate management port
-      # @param trusted_certs     [Array]   (Params) Optional list of files with trusted certificates (stores)
-      # @param client_ssh_key    [String]  (Params) Client SSH key option (from CLIENT_SSH_KEY_OPTIONS)
-      # @param check_ignore_cb   [Proc]    (Params) Callback with host,port
+      # (Args) : Options that influence `ascp` arguments.
+      #
+      # @param ascp_args         [Array]   (Args) Optional Additional arguments to ascp
+      # @param wss               [Boolean] (Args) `true`: if both SSH and wss in ts: prefer wss
+      # @param quiet             [Boolean] (Args) By default no native `ascp` progress bar
+      # @param client_ssh_key    [String]  (Args) Client SSH key option (from CLIENT_SSH_KEY_OPTIONS)
+      # @param trusted_certs     [Array<String>] (Args) (WSS) Optional list of files with trusted certificates (stores)
+      # @param check_ignore_cb   [Proc]    (Args) (WSS) Callback with host,port to check if WSS connection shall ignore certificate validity
       # @param spawn_timeout_sec [Integer] Timeout for ascp spawn
       # @param spawn_delay_sec   [Integer] Optional delay to start between sessions
       # @param multi_incr_udp    [Boolean] Optional `true`: increment UDP port for each session
       # @param resume            [Hash]    Optional Resume policy
+      # @param monitor           [Boolean] Set to `false` to eliminate management port
       # @param management_cb     [Proc]    callback for management events
       # @param base_options      [Hash]    other options for base class
       def initialize(
         ascp_args:         nil,
         wss:               true,
         quiet:             true,
-        trusted_certs:     nil,
         client_ssh_key:    nil,
+        trusted_certs:     nil,
         check_ignore_cb:   nil,
         spawn_timeout_sec: 2,
         spawn_delay_sec:   2,

data/lib/aspera/agent/factory.rb

@@ -22,11 +22,11 @@ module Aspera
         Dir.children(File.dirname(File.expand_path(__FILE__)))
           .select{ |file| file.end_with?(Environment::RB_EXT)}
           .map{ |file| File.basename(file, Environment::RB_EXT).to_sym}
-          .reject{ |item| IGNORED_ITEMS.include?(item)}.each_with_object({}) do |agent_sym, hash|
-          hash[agent_sym] = {
+          .reject{ |item| IGNORED_ITEMS.include?(item)}.to_h do |agent_sym|
+          [agent_sym, {
             long:  agent_sym.to_s.capitalize,
             short: agent_sym.eql?(:direct) ? :a : agent_sym.to_s[0].to_sym
-          }.freeze
+          }.freeze]
         end.freeze
       private_constant :IGNORED_ITEMS
     end

data/lib/aspera/agent/node.rb

@@ -59,7 +59,7 @@ module Aspera
         ts_tags = transfer_spec['tags']
         ts_tags[Transfer::Spec::TAG_RESERVED]['xfer_retry'] ||= 150 if ts_tags.is_a?(Hash) && ts_tags[Transfer::Spec::TAG_RESERVED].is_a?(Hash)
         # Optimization in case of sending to the same node
-        # TODO: probably remove this, as /etc/hosts shall be used for that
+        # TODO: probably remove this, as /etc/hosts shall be used for that on server side.
         transfer_spec['remote_host'] = '127.0.0.1' if !transfer_spec['wss_enabled'] && transfer_spec['remote_host'].eql?(URI.parse(node_api_.base_url).host)
         resp = node_api_.create('ops/transfers', transfer_spec)
         @transfer_id = resp['id']

data/lib/aspera/api/alee.rb

@@ -3,6 +3,7 @@
 require 'aspera/api/aoc.rb'
 module Aspera
   module Api
+    # Aspera License Entitlement Engine API client
     class Alee < Aspera::Rest
       def initialize(entitlement_id, customer_id, api_domain: AoC::SAAS_DOMAIN_PROD, version: 'v1')
         super(