mirror of
https://github.com/asdf-vm/asdf.git
synced 2024-11-15 01:28:17 -07:00
0e8e1f8f84
It's possible for plugins to define new asdf commands. This way plugins can extend asdf capabilities or expose utilities related to their managed tool. For example, a `foo` plugin might expose the command `asdf foo bar` by providing an executable file at `bin/bar`. If `bin/bar` is a file but has no executable bit set, then its considered a source-able bash script, and will be sourced with all the functions in `$ASDF_DIR/lib/utils.sh` already loaded. A good example of this feature is the `nodejs` plugin, where people must import the release team keyring before installing a nodejs version. People can execute the following command without having to know where exactly is the plugin located. |
||
|---|---|---|
| .. | ||
| fixtures | ||
| asdf_fish.bats | ||
| asdf_sh.bats | ||
| banned_commands.bats | ||
| current_command.bats | ||
| get_asdf_config_value.bats | ||
| install_command.bats | ||
| latest_command.bats | ||
| list_command.bats | ||
| plugin_commands.bats | ||
| plugin_extension_command.bats | ||
| plugin_list_all_command.bats | ||
| plugin_test_command.bats | ||
| remove_command.bats | ||
| reshim_command.bats | ||
| shim_env_command.bats | ||
| shim_exec.bats | ||
| shim_versions_command.bats | ||
| test_helpers.bash | ||
| uninstall_command.bats | ||
| update_command.bats | ||
| utils.bats | ||
| version_commands.bats | ||
| where_command.bats | ||
| which_command.bats | ||