Commit Graph

205 Commits

Author SHA1 Message Date
Daniel Perez
77a748d70a
fix: _where_ bug when multiple versions are selected (#790)
Fixes #690
2020-08-28 19:24:59 +10:00
James Hegedus
8ca2af3316
feat: cmd to print debug information (#787) 2020-08-24 10:55:41 +10:00
Trevor Brown
cc0023b022
feat: plugin documentation callback support 🎉 (#757) 2020-07-31 18:47:18 +10:00
James Hegedus
a5c815b6d4
fix: print tool-versions file dir on shim error (#750) 2020-07-31 18:46:33 +10:00
Dan Fuchs
d7e1e66c03 Add test for invalid asdf install arguments 2020-07-09 21:18:16 -05:00
Dan Fuchs
6a1855e26f Install one tool specified in .tool-versions
`asdf install <name>` installs that single tool at the version specified
in `.tool-versions`.  If there is no `.tool-versions` or if that tool is
not in it, an error message is shown and `asdf` exits `1`.

Implements #759
2020-07-09 18:16:50 -05:00
Trevor Brown
aef4ae8b5a
fix: ban the sort -V command (#755) 2020-07-08 15:37:52 +10:00
Trevor Brown
4219f9f5b1 Add column to list of banned commands for the asdf codebase 2020-07-06 09:47:35 -04:00
Thomas B Homburg
1b7b4da0a6
fix: remove column command in favor of awk (#721) 2020-06-17 08:26:46 +10:00
Alexandre ZANNI
f5c7dae331
fix: asdf shell command docs & help output (#737)
Co-authored-by: James Hegedus <james@jthegedus.com>
2020-06-13 10:43:52 +10:00
Aravinda Rao
fe26274f38 Ensure consistency in indentation for message shown when no versions installed 2020-05-18 21:48:27 +05:30
Trevor Brown
410f414529 Remove downloads when removing a plugin 2020-05-14 09:13:51 -04:00
Trevor Brown
d65283548f
Fix formatting issue 2020-05-08 14:15:21 -04:00
Trevor Brown
2a058af9eb
Merge branch 'master' into tb/keep-source 2020-05-08 10:21:59 -04:00
Trevor Brown
309a4f1a12 Don't delete the download directory if the --keep-download flag is passed or the always_keep_download config is set to yes 2020-05-04 15:05:10 -04:00
Trevor Brown
5c6f24f1ce Add basic tests for legacy plugins 2020-05-04 11:18:31 -04:00
Trevor Brown
0e0922a014 Add unit test for plugin add exit code 2020-03-31 09:20:10 -04:00
Jochen Schalanda
3c3f0e67f6
Rename custom plugin-add/plugin-remove for plugins (#684)
Rename custom scripts for `plugin-add` and `plugin-remove` phases in plugins to make clear when they are executed:

`plugin-add` -> `post-plugin-add`
`plugin-remove` -> `pre-plugin-remove`
2020-03-22 12:57:54 +11:00
Jochen Schalanda
95d4c07294
Set Git user and email in tests 2020-03-21 15:12:01 +01:00
Jochen Schalanda
57186be6d9
Support customizing plugin-add and plugin-remove
* Add support for custom `plugin-add` and `plugin-remove` in plugins
* Add configurable command hooks for plugin installation and removal

```shell
pre_asdf_plugin_remove = echo will remove plugin ${1}
pre_asdf_plugin_remove_foo = echo will remove plugin foo
post_asdf_plugin_remove = echo removed plugin ${1}
post_asdf_plugin_remove_foo = echo removed plugin foo
```

Closes #670
2020-03-21 14:59:33 +01:00
Victor Hugo Borja
a26bed6586 Make sure extension commands are properly displayed by asdf help 2020-03-15 11:45:09 -06:00
Jochen Schalanda
609e41e276 Use different exit code if updates are disabled
If asdf-vm was installed with a package manager and the user doesn't
have the necessary permissions to update it with `asdf update`, asdf-vm
emits an informational message and exits with exit code 1.

This makes it hard to programmatically detect whether the update failed
or wasn't even attempted because it's not possible.

With this change, asdf-vm would exit with the exit code 42 if updates are
disabled instead of exit code 1, which signals an error during update.

Refs r-darwish/topgrade#367
2020-03-13 10:14:28 +01:00
Trevor Brown
7a05244ece Add legacy plugin fixture 2020-03-06 19:13:53 -05:00
Trevor Brown
91a2a1f7be Add get_download_path function 2020-03-06 18:54:33 -05:00
Trevor Brown
8b90d883ee Require .bash extension for plugin extension commands 2020-03-02 13:13:20 -05:00
Trevor Brown
52cbf1165c Add .bash file extensions to files containing code executed by Bash 2020-03-02 12:48:05 -05:00
Victor Borja
62c4fdb163
Merge pull request #623 from jonmast/prevent-exec-recursion
Ignore shim directory for executable lookups
2020-02-14 14:26:03 -06:00
Trevor Brown
42182f31c4 Add test for shim exec of path versions 2020-02-07 22:32:04 -05:00
Trevor Brown
e4a9ad6e58
Merge pull request #649 from asdf-vm/tb/misc-test-improvements
Misc. Test Improvements
2020-02-05 07:51:42 -05:00
Trevor Brown
6d8d77f51d Unset ASDF_DIR variable before running tests 2020-02-04 11:23:09 -05:00
Trevor Brown
f787b719ac
Merge pull request #640 from asdf-vm/improve-export-shell
Fix asdf shell xx --unset for fish
2020-02-04 08:17:54 -05:00
Trevor Brown
79ffc55f82 Add another test for asdf_data_dir function 2020-01-31 14:03:33 -05:00
Trevor Brown
84ab5b7753 Fix hanging 'asdf update is a noop for non-git repos' test 2020-01-29 09:58:59 -05:00
Daniel Perez
e53de6726f Fix asdf shell xx --unset for fish 2020-01-25 20:42:43 +00:00
Timo Sand
09db5d6bfc
Switches to actually use latest instead of first 2019-12-30 23:25:56 +02:00
Timo Sand
340b027b5f
Removes echo overcomplication 2019-12-30 21:03:38 +02:00
Jonathan Mast
069c74f45e
Ignore shim directory for executable lookups
Previously, the shims directory was only excluded for system versions,
which meant that `asdf exec` would fall back to a shim if the install
didn't have the desired binary. If the shims are up to date this isn't a
problem since we check the metadata, but it causes issues if those are
out of sync for whatever reason.

I've checked all the uses of this function and I'm not seeing anywhere
we should need the old behavior.
2019-12-21 15:24:55 -05:00
Jonathan Mast
67e0e50445
Run config tests in BATS_TMPDIR for clean environment
This avoids issues with it picking up config files from parent
directories.
2019-12-21 14:22:32 -05:00
Luke Bonaccorsi
c728018627 Fix issue with preset version warning assuming that the shim name and plugin name are the same 2019-12-20 17:26:00 +00:00
Victor Borja
ff57001691
Merge pull request #609 from tejanium/clearer-warning
Clarify instructions when <version> of a <shim_name> is missing.
2019-12-13 12:02:16 -06:00
Teja Sophista
026aa78f35 Output different warning for empty and missing version
1. when `.tool-versions` is not set
2. when `.tool-versions` set version that is not installed
2019-12-04 14:18:58 +00:00
Victor Hugo Borja
5ab01f49df Allow eval only on asdf function at lib/asdf.sh.
It's needed for `asdf shell` command.
2019-12-03 11:04:04 -06:00
Victor Hugo Borja
3d3595c7a3 Improvements to asdf plugin commands. 2019-11-30 14:18:37 -06:00
Victor Hugo Borja
b8dc5f1604 Run shfmt on bash files 2019-11-29 10:15:38 -06:00
Victor Hugo Borja
83dc1712e3 Change to test HOME on test setup 2019-11-27 12:25:34 -06:00
Victor Hugo Borja
e968fe6142 Subcommand-aware command line interface. 2019-11-27 12:17:17 -06:00
Victor Hugo Borja
70099027c2 Move plugin extension command into it's own file.
Add a test for calling default command with arguments.
2019-11-25 12:07:55 -06:00
Victor Hugo Borja
a22733f819 Resolve asdf PLUGIN_NAME default command.
When calling `asdf foo` and the `foo` plugin provides a `bin/default-command`
2019-11-25 02:47:55 -06:00
Victor Hugo Borja
0e8e1f8f84 New feature: asdf extension commands
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.
2019-11-25 02:24:46 -06:00
Kevin Lane
c11409583f
Add unit tests for managing latest stable versions 2019-11-22 10:37:53 -08:00