github.com/criteo/command-launcher@v0.0.0-20230407142452-fb616f546e98/gh-pages/content/en/blog/1.8.0-release-notes.md (about)

     1  ---
     2  title: "✨ 1.8.0 Release"
     3  description: "Command launcher 1.8.0 Release"
     4  excerpt: "Command launcher 1.8.0 Release"
     5  date: 2023-01-02T09:19:42+01:00
     6  lastmod: 2023-01-02T09:19:42+01:00
     7  draft: false
     8  weight: 50
     9  images: []
    10  categories: ["News"]
    11  tags: ["release"]
    12  contributors: ["Bo HOU"]
    13  pinned: false
    14  homepage: false
    15  ---
    16  
    17  ## Release notes
    18  
    19  * ✨Support multiple remote registry. From version 1.8.0, you are able to define multiple remote registries. Command launcher synchronizes the commands with all these remote registries at the end of each command execution. This is useful for several scenarios: for example, supporting internal or experimental commands, different teams target their commands to different group of audience.
    20  * ✨Built-in command `remote` command to mange multiple remote registries.
    21    * `remote list`: list all remote registries
    22    * `remote delete`: delete specific remote registry
    23    * `remote add`: add a new remote registry
    24  * ✨Built-in package management related commands are regrouped into `package` command:
    25    * `package list`: list installed local and dropin packages and remote packages. It also provides the possibility to show the installed commands
    26    * `package install`: install dropin packages from git repository or remote/local zip file
    27    * `package delete`: delete installed dropin packages
    28  * ✨New command name conflict resolution system: Each command now has a unique full name in form of [regitry]@[package]@[group]@[name]. When two commands register to the same group and name. One of them will be registered with its full group name.
    29  
    30    For example, two command `hello@greeting@pkg1@repo1` and `hello@greeting@pkg2@repo2`. These two commands have the same group name and command name (greeting hello). The first one will be registered as `cola greeting hello`, the second one will be registered as command `cola greeting@@pkg2@repo2 hello`. Note: `greeting@@pkg2@repo2` is the full name of the group command `greeting` defined in pkg2 and repo2.
    31  * ✨New built-in `rename` command. Now it is possible to rename both group and sub command to a different name.
    32  * ✨New resource `PACKAGE_DIR`. Each command now can access its package's absolute path through the `PACKAGE_DIR` resource. This resource doesn't require user consent.
    33  
    34  * 🔥Metrics system hook interface change. Now the metrics system hook accepts two new parameters: repo/registry name, package name. The full list of parameters:
    35    1. repository/registry name (see remote command)
    36    2. package name
    37    3. command group name, or “default” if no group
    38    4. command name
    39    5. user partition
    40    6. command exit code
    41    7. command execution duration in nano seconds
    42    8. error message or “nil” if no error
    43    9. command start timestamp in seconds