Provide a flag or configuration option to allow `asdf install` to continue when missing plugins are found in .tool-versions
- Dominant language
- Go
- Stars
- 25.6k
- Forks
- 941
- Avg merge
- 9h 24m
- Merged PRs (30d)
- 3
Description
> I think we should stop installing when a missing plugin is encountered. Some projects define plugins in the order they must be installed in, because certain plugins depend on others. Proceeding to install subsequent versions after a plugin is not found could cause problems.
This change breaks my workflow as I intentionally do not install all plugins on all my machines (depending on which I need). Is there any way to disable this feature (looking at the code I guess no) or make it so it can be disabled?
_Originally posted by @cmur2 in https://github.com/asdf-vm/asdf/issues/1033#issuecomment-991784380_
Contributor guide
Research direction
Start at the `asdf install` handling for missing plugins and review how `.tool-versions` entries are processed. Compare the behavior described here with issue 1033, then define the option's expected behavior so users can continue past missing plugins without changing the existing default ordering and stopping behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100