What's Changed
Confirmation
If the generated command contains some specific flags (like --volume, --mount, --privileged, --publish, --publish-all, --network and --pid) the user will be asked to confirm before to run. That adds a guard to ensure for instance the user is not sharing files they don't want without to know.
A --yes can be used on the command line to skip the confirmation, or by adding accept-the-risk: true in the local .docker/runx.yaml configuration file.
Prompts
Default values are now supported for all types of user prompts and a new boolean prompt is now available.
This introduces a new type field for opts that can be one of input, select or confirm. Default value can be set using default field.
Some improvements have been made regarding the display of the prompt title and description.
Help
-h or --help are now the default way to print the readme or the help for an action instead of the previous -d or --docs. This makes it easier to discover.
Cache
When a docker runx manifest is read, the corresponding files are cached locally under ~/.docker/runx/cache directory. It comes with two new commands docker runx cache df to display the disk usage and docker runx cache prune to clean it.
In addition and in order to reduce the need of those commands, all cached items not accessed in the last 30 days will be automatically removed at each run. That way the cache stays clean without any user action.
Other improvements
-
To match between the user input and the different config files, the reference of the image is used instead of the input. So for instance
namespace/imagewill matchdocker.io/namespace/image:latest -
Improve yaml string reading to set the command with
>and|
Full Changelog: v0.0.20...v0.1.0