Releases: criteo/command-launcher
Releases · criteo/command-launcher
1.14.0
✨ New Features and Updates
- Extra remote registry now support different sync policies: hourly, daily, weekly, and monthly. For the first iteration, the sync_policy configuration can only be modified in the configuration file. A built-in command will be provided in the future release to manage these sync policies.
- LOG_LEVEL and DEBUG_FLAGS no longer requires user consent.
🐛 Bug Fixes
- built-in update command now take into account the extra remote registries, and respect the sync_policy configuration for each registry.
📝 Documentation Updates
- Update configuration documentation to reflect the new sync_policy configuration and user consent resources.
1.13.0
✨ New Features
- built-in login command now look for three environment variables for the default user name (in order):
${APP_NAME}_USERNAME,$USER, and$USERNAME. The default user is also printed in the output to avoid confusion. - a new resources
{APP_NAME}_FULL_COMMAND_NAMEwill be passed to the managed command. This environment variable contains (separated by space):- the command launcher binary name
- the command group name (if any)
- the command name
- a new boolean type configuration item
group_help_by_registryto allow the user to group the top level commands by registry in the help message. The default value is true.
New Contributors
1.12.1
✨ Add a linux ARM64 variant of command-launcher.
1.12.0
- 🐛 Fix the issue that zip extraction fails due to the size of the extracted file
- ✨ Add new option
--timeoutto the built-inupdatecommand, and set the default timeout to 10 seconds - ✨ Improve autocomplate performance by applying filter in command launcher
- ✨ Pass
[APP_NAME]_TO_COMPLETEenvironment variable to the auto-complete extension command, this can be used to filter the auto-complete results in the extension command - ⬆️ Update golang version to 1.22.0 on the CI
1.11.1
- 🐛 Fix change package internal folder permission issue after unzip
1.11.0
- 🐛 Fix 403 error when downloading package from Github
- ✨ Login hook now supports any key value pair to be stored as a credential. Before it is limited to username, password, and token.
- 🚸 Ensure folder in the package have the correct permission.
- ⬆️ Update cobra version to 1.7.0, viper version to 1.16.0
1.10.1
- 🐛 Fix regression: flags aren't passed to
validArgsCmdwhencheckFlagsis true.
1.10.0
- ✨ Support auto-complete for flag values. Introduced two new flag properties
valuesfor static flag values andvaluesCmdfor dynamic flag values. - ✨ New
--listoption in the built-in rename command to list all command alias - 🐛 Fix wrong exit code reported in metrics.
1.9.0
- ✨New package level system command
__setup__. This system hook can be triggered once a new package version is installed from the remote registry. Or manually triggered from the built-inpackage setupcommand.- New configuration
enable_package_setup_hookto toggle the new package setup hook during package installation - New built-in command
package setupto manually trigger the package setup system hook
- New configuration
- ✨New ways to define command flags. The newly introduced
flagscommand property allows you to define the command flags with an object instead of the formatted string separated by\t. TherequiredFlagsproperty can be stilled be used to define flags, but it is marked as deprecated. - ✨New
exclusiveFlagscommand property to ensure that only one property can be specified among a set of flags. This property must be used together with thecheckFlagsproperty to delegate the command launcher for argument parsing - ✨New
groupFlagscommand property to ensure that all of them must be specified from the command line among a set of flags. This property must be used together with thecheckFlagsproperty to delegate the command launcher for argument parsing
1.8.1
- 🐛 Fix DNS resolve issue on darwin amd64 under VPN. For Mac intel user, please download this version.