Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Print a line mentioning what plugin/version is currently being installed #1753

Open
StingRayZA opened this issue May 10, 2024 · 1 comment · May be fixed by #1754
Open

Print a line mentioning what plugin/version is currently being installed #1753

StingRayZA opened this issue May 10, 2024 · 1 comment · May be fixed by #1754

Comments

@StingRayZA
Copy link

Is your feature request related to a problem? Please describe

If you run asdf install on a project with multiple tools defined in .tool-versions you get hit with a wall of output from the various tools being installed/built/etc. This is fine, but if an error occurs with one of those (in an automated process, perhaps - like CI) it can be quite difficult to figure out exactly where the error has occurred.

On the other hand, if those tools are already installed, asdf outputs a line similar to package 1.2.3 is already installed.

It would be good to add installing package 1.2.3 into the "wall of output" so somebody trying to pick through the history of a failing bulk install has at least a breadcrumb to go on.

Describe the proposed solution

when installing a plugin, the following outputs:

package 1.2.3 is downloading
package 1.2.3 is installing

or similar

Describe similar asdf features and why they are not sufficient

running asdf install on already installed tools already outputs a readable line, but this isn't helpful in automated jobs

Describe other workarounds you've considered

I considered breaking up our install into separate invocations of asdf, but the tool already has the ability to process the .tool-versions file and install any missing tools.

@jthegedus
Copy link
Contributor

Yes, this makes complete sense. Shocked it hasn't been raised before now 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants