Describe the bug
I'm not sure if this is the right place to report this, but the listed jq plugin (https://github.com/focused-labs/asdf-jq) is unstable and seems not to be maintained anymore (open issues and PRs with no response, no commits for over a year, etc).

There's a fork mentioned in an issue there (focused-labs/asdf-jq#6) that looks to have more activity and is more stable (https://github.com/AZMCode/asdf-jq). It's not my fork, but I wanted to point out that I had lots of trouble installing with the default plugin, and @AZMCode 's fork worked perfectly first try.

Describe the Bug

The terragrunt plugin does not work on ARM64.

I proposed a fix via a fork but the maintainer did not reply after a month.

I suggest updating the terragrunt plugin URL to https://github.com/ohmer/asdf-terragrunt since it contains the bug fix.

Steps to Reproduce

On a ARM64 machine, install terragrunt plugin:
asdf plugin add terragrunt

Expected Behaviour

Terragrunt binary for ARM64 installed with pinned version.

Actual Behaviour

Terragrunt binary for AMD64 installed with pinned version.

Environment

OS:
Linux ip-10-0-0-238 5.11.0-1019-aws #20~20.04.1-Ubuntu SMP Tue Sep 21 10:41:13 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

SHELL:
fish, version 3.3.1

ASDF VERSION:
v0.8.1-a1ef92a

ASDF ENVIRONMENT VARIABLES:
ASDF_DIR=/home/ohmer/.asdf

ASDF INSTALLED PLUGINS:
terragrunt                   https://github.com/lotia/asdf-terragrunt.git

We need to specify the licenses we permit. It seems reasonable to me to only permit open source licenses for plugins, but I don't think we've ever had that as a hard requirement.

Describe the Bug

It looks like there has been no maintainer activity in this repo since mid-December. All PRs opened since then are still waiting to get reviewed.

Steps to Reproduce

https://github.com/asdf-vm/asdf-plugins/pulls?q=is%3Apr+is%3Amerged

Expected Behaviour

Hard to tell as this is a community project so I would like to offer help get some of the PRs over the line because 2 months of no activity feels a little too long. 🙂

Actual Behaviour

see above

Environment

n/a

https://devspace.sh/

Fn Project – https://fnproject.io/

Is your feature request related to a problem? Please describe.

The problem:
Now that there's plenty of plugins being supported by asdf, the plugin list may seem like a random word list that doesn't really describe what each plugin does or to what project it belongs, leaving the user hung up on the relationship between a plugin and the project it relates to.

Describe the solution you'd like

Add another column to the "All Plugins" section called "Project URL" that links to the base project.

Describe similar asdf features and why they are not sufficient

There's nothing in asdf right now that points to the project a plugin may relate to.
The only option is to click on the plugin link listed and hope the author of the plugin has a link somewhere that explains to what project their plugin is related.

Describe workarounds you've considered

Just as a start it would be nice to have a third column in the "All plugins" section of the asdf website, but ideally there should be more info about this in the plugin itself in both the plugin codebase and the plugin info in the asdf cli.

Additional context

The idea is really that simple and it comes from the frustration of browsing through the plugins list and finding that some of them have no reference to the core project they relate to. This is not only useful for beginners that just wanna find new tools to work with, but also for more seasoned people who really don't know what every plugin is for.

I can create a PR to begin with, but it would be ideal that this becomes a standard for new plugins. So to get listed, you should also add basic info that points to the core project your plugin relates to in both the plugin codebase and asdf website.

The repository for the asdf jq plugin has an issue regarding release asset selection

To Reproduce
Run the following commands on a linux box with asdf and the jq plugin.

$ asdf install jq jq-1.6

jq-1.6 can be replaced by any other jq version available.

Expected behavior

Jq Linux release selected and installed

Actual behavior

Linux release for jq not found

Environment

OS: Linux

asdf version: any

asdf plugins affected (if relevant): jq

asdf plugins installed: jq

Additional context
Pull request fixing the issue has been posted on the issue more than a month ago, and there's been no activity on the part of the maintainer

Hi, I have a plugin that fails list-all in OSX but not Linux and am hoping to get some pointers from OSX users.

• failed osx test: https://travis-ci.org/td7x/asdf-terragrunt/jobs/360733037
• pass linux test: https://gitlab.com/td7x/asdf/terragrunt/-/jobs/48771595

list-all:

#!/usr/bin/env bash

releases_path=https://api.github.com/repos/gruntwork-io/terragrunt/releases
cmd="curl -s $releases_path"

function sort_versions() {
  sed 'h; s/[+-]/./g; s/.p\([[:digit:]]\)/.z\1/; s/$/.z/; G; s/\n/ /' | \
    LC_ALL=C sort -t. -k 1,1 -k 2,2n -k 3,3n -k 4,4n -k 5,5n | awk '{print $2}'
}

echo $(eval "$cmd" | grep -oE "tag_name\": \".{1,15}\"," | sed 's/tag_name\": \"v//;s/\",//' | sort_versions)

I see that there is an Oracle Java plug-in already, but I think it would be nice to have also (or instead) the OpenJDK's ‒ at least from version 8.x onwards; the previous ones, while deprecated now, were pretty nasty to install.

Is your feature request related to a problem? Please describe

No

Describe the proposed solution

Implement plugin for Kafcat.

Describe similar asdf features and why they are not sufficient

N/A

Describe other workarounds you've considered

Manually install and manage Kafcat versions.

I'm not sure how possible this might be, but the v2 and v1 processes are quite different, so it might require 2 plugins? 🤷‍♂ Also not sure if it's possible to target specific v2 versions

See:

• https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html
• https://docs.aws.amazon.com/cli/latest/userguide/install-cliv1.html

Is your feature request related to a problem? Please describe

N/A

Describe the proposed solution

Add @amrox's pyapp plugin: https://github.com/amrox/asdf-pyapp/ to the README.

Describe similar asdf features and why they are not sufficient

N/A

Describe other workarounds you've considered

N/A

Describe the Bug

Attempting to install a version of Flutter fails due to missing command jq. Luckily asdf also has a plugin for jq, but I would expect plugin dependencies to be managed in some way.

Steps to Reproduce

$ asdf install flutter latest

Expected Behaviour

$ asdf install flutter latest

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 1121M  100 1121M    0     0  7402k      0  0:02:35  0:02:35 --:--:-- 8777k

Actual Behaviour

$ asdf install flutter latest

~/.asdf/plugins/flutter/bin/install: line 25: jq: command not found
~/.asdf/plugins/flutter/bin/install: line 26: jq: command not found
~/.asdf/plugins/flutter/bin/install: line 27: [: -gt: unary operator expected
Cannot find the download url for the version: 2.10.4-stable

Environment

MacOS 11.5.2

OS:
Darwin toines-mbp.home 20.6.0 Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:31 PDT 2021; root:xnu-7195.141.2~5/RELEASE_X86_64 x86_64

SHELL:
zsh 5.8 (x86_64-apple-darwin20.0)

ASDF VERSION:
v0.9.0

ASDF ENVIRONMENT VARIABLES:
ASDF_DIR=/usr/local/opt/asdf/libexec

ASDF INSTALLED PLUGINS:
poetry                       https://github.com/asdf-community/asdf-poetry.git master 7ea77b0
python                       https://github.com/danhper/asdf-python.git master 57a4d72

Current default sbt plugin is using bin tray that is somehow stuck in the past (at release 1.0.0-M4, while current sbt release is 1.2.8)

I'm using this other plugin that uses GitHub API to retrieve sbt releases.

I'm making a PR for this.

Thanks

https://podman.io/

Is your feature request related to a problem? Please describe

No.

Describe the proposed solution

Implement plugin for Venom.

Describe similar asdf features and why they are not sufficient

N/A

Describe other workarounds you've considered

Manually install and manage Venom versions.

https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html

See https://haxe.org/

Actually, I don't know if it's possible to have Git as an asdf plugin, but I'm just filing this one just in case 😎

Describe the Bug

#607 caused a breaking change to adding pnpm versions older than 6.12

Steps to Reproduce

Put the following in your .tool-versions file
pnpm 6.6.1

Run the commands:

asdf plugin add pnpm
asdf install

Expected Behaviour

pnpm 6.6.1 should install

Actual Behaviour

asdf is unable to download and install pnpm

$ asdf install
nodejs 14.19.1 is already installed
* Downloading pnpm release 6.6.1...
curl: (22) The requested URL returned error: 404 
asdf-pnpm: Could not download https://github.com/pnpm/pnpm/releases/download/v6.6.1/pnpm-macos-x64
cp: cannot stat '/Users/me/.asdf/downloads/pnpm/6.6.1/pnpm-6.6.1': No such file or directory
chmod: cannot access '/Users/me/.asdf/installs/pnpm/6.6.1/bin/pnpm': No such file or directory
asdf-pnpm: Expected /Users/me/.asdf/installs/pnpm/6.6.1/bin/pnpm to be executable.
asdf-pnpm: An error ocurred while installing pnpm 6.6.1.

Environment

OS:
Darwin C02XK03SKQCJ 20.6.0 Darwin Kernel Version 20.6.0: Wed Nov 10 22:23:07 PST 2021; root:xnu-7195.141.14~1/RELEASE_X86_64 x86_64 i386 MacBookPro15,1 Darwin

SHELL:
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin20)
Copyright (C) 2007 Free Software Foundation, Inc.

ASDF VERSION:
v0.8.1

ASDF ENVIRONMENT VARIABLES:
ASDF_DIR=/usr/local/Cellar/asdf/0.8.1_1/libexec

ASDF INSTALLED PLUGINS:
nodejs                       [email protected]:asdf-vm/asdf-nodejs.git
pnpm                         [email protected]:technikhil314/asdf-pnpm.git

Is your feature request related to a problem? Please describe

Currently, each plugin has its own repository, owner, and per consequence development/review process and opinions.

Having the official plugins in such a fashion can be very insecure as the repositories can be exposed to bad actors, either with the consent of the plugin maintainers or by accident, via faulty reviews or security leaks of said accounts. Plugins can also be abandoned or deleted at will.

This is in my opinion a huge security threat, as we can't blindly trust all the different parties involved in plugins installs and updates.

Describe the proposed solution

Similar to how other tools handle it (homebrew, nixpkgs, oh-my-zsh) would be to keep all the plugins in a single repository.

Benefits:

• Changes would be reviewed in a standardized manner and in a controlled fashion. All PRs could be audited for security and deviations of the asdf-core philosophy.
• We could easily address updates and security fixes.
• Testing all packages could be a lot better. And installing/updating plugins could be simplified, as we wouldn't necessarily need to run plugin-add, all plugins would already be installed always.

I could work on this solution if the idea ever gets greenlighted.

Describe similar asdf features and why they are not sufficient

NA

Describe other workarounds you've considered

NA

Is your feature request related to a problem? Please describe

It is not a problem. I just wanted to share the plugin I have created for `kubevela' https://kubevela.io

Describe the proposed solution

The plugin is located at
https://github.com/josephlim75/asdf-kubevela.git

Describe similar asdf features and why they are not sufficient

none

Describe other workarounds you've considered

none

Describe the Bug

My dotbot setup stopped working with a weird error:

Unknown plugin: stern                                                                                                                                                                                                                          
Please provide URL                                                                                                                                                                                                                             
                                                                                                                                                                                                                                               
==> Some tasks were not executed successfully    

But I already had stern installed. The problem was introduced by #652 because the file it added doesn't have the repository property set, i.e.:

repository = https://github.com/asdf-community/asdf-link.git 

this problem also makes not possible to install the link plugin

$ asdf plugin add link          
plugin link not found in repository

Steps to Reproduce

1. Try to install link

$ asdf plugin add link          
plugin link not found in repository

or

2. Try to install any package listed after link using asdf-dotbot plugin

Unknown plugin: stern                                                                                                                                                                                                                          
Please provide URL                                                                                                                                                                                                                             
                                                                                                                                                                                                                                               
==> Some tasks were not executed successfully    

Expected Behaviour

Link plugin should be installed

Actual Behaviour

Link plugin can't be installed and asdf-dotbot plugin stop working for any plugin listed after link using asdf plugin-list-all

Environment

$ asdf --version
v0.10.2-7e7a1fa

Describe the bug

The bazel plugin listed in the README does not work.

The repository https://github.com/rajatvig/asdf-bazel hasn't been updated since Dec 2018 and issues are not enabled

To Reproduce

Tell us what actions you performed before the issue occurred

Steps to reproduce the behavior:

$ asdf plugin-add bazel https://github.com/rajatvig/asdf-bazel.git
$ asdf install bazel latest                                                                                                                                                                                                                                                
Bazel installer
---------------

Bazel is bundled with software licensed under the GPLv2 with Classpath exception.
You can find the sources next to the installer on our release page:
   https://github.com/bazelbuild/bazel/releases

# Binary package at HEAD (@df2f77c2a8)
   - [Commit](https://github.com/bazelbuild/bazel/commit/df2f77c2a8)
Uncompressing......%

$ asdf list bazel                                                                                                                                                                                                                                                          
  No versions installed

Expected behavior

Bazel to be installed

Actual behavior

$ which bazel                                                                                                                                                                                                                                                              
bazel not found

$ ls  ~/.asdf/installs/bazel

Environment

OS:

asdf version: v0.8.0

asdf plugins affected (if relevant): bazel

asdf plugins installed:

asdf plugin-list                                                                                                                                                                                                                                                         
bazel

Additional context

Remove plugin from docs if the repo is not maintained anymore.

We've been trying to figure out how to better manage asdf plugins for months. As a result, the asdf-community works relatively well with the help of the community, and it seems like a good idea to mention it in the README. What do you think?

https://github.com/asdf-community/.github

I love ASDF, and would like to contribute more, and possibly be a maintainer. It seems there are PRs piling up that could use merging, and direction to resolution.

Can I help?

The R plugin is not currently being maintained. The plugin is working well enough but see iroddis/asdf-R#8 and iroddis/asdf-R#6 for evidence of the plugin's lack of maintenance. I'm happy to maintain this for the foreseeable future, opening a PR to that effect.

It would be great to be possible to install Micronaut, in the same way the SDKMAN! tool manager provides.

The maven plugin is unmaintained and broken. I have forked it, applied pull requests and will actively maintain it. I am the current maintainer of asdf-java and asdf-clojure.

Please see PR #146

Is your feature request related to a problem? Please describe

I'd like to have a project local Firefox profile, with a optional customized user.js from Arkenfox.

I know there's https://github.com/vincentvanbush/asdf-firefox but installing it using asdf direnv local fails:

asdf direnv local firefox latest
▶ asdf plugin-add firefox # ...  plugin firefox not found in repository
✔️
▶ asdf install firefox latest # ...  No such plugin: firefox
❗️ Failed with status 1

This is just about the extent of what I know about the problem, which I'm ready to solve if someone can point me in the right direction along the way. Where do I start?

Describe the proposed solution

1. Add a firefox plugin that can be used with asdf direnv local
2. Add a arkenfox plugin that can be used with asdf direnv local and injects the requested version of Arkenfox in the currently configured firefox profile
3. In 2. protect against existing user customization overrides

Describe similar asdf features and why they are not sufficient

• There is to my knowlege no firefox plugin that works out of the box with asdf direnv local.
• https://github.com/vincentvanbush/asdf-firefox does not verify any checksum or signature.

Describe other workarounds you've considered

I've tried adding a user.js directly in '$HOME/.mozilla/firefox/'
I don't like messing with this HOME directory, and the profile names look absolutely horrible.
I'd rather have a local .firefox directory in a project-local directory, with a user.js file that symlinks
to a project.local Arkenfox user.js.

We are currently considering removing all test failed plugins from the README. Do you have the bandwidth to fix so that the test runs correctly again. Whether you have bandwidth or not, we recently started a collaborative, community-driven project called asdf-community for long-term maintenance of asdf plugins, so consider moving your plugins here.
https://github.com/asdf-community/.github

I'm tagging all the authors of the related plugin (in no particular order), but I'd like to hear everyone's opinions.

• @Ibotta (Ibotta/asdf-brig)
• @marciogm (marciogm/asdf-crystal)
• @mikestephens (mikestephens/asdf-elasticsearch)
• @vic (vic/asdf-graalvm)
• @vic (vic/asdf-haskell)
• @rkyleg (rkyleg/asdf-julia)
• @sylph01 (sylph01/asdf-mongodb)
• @richin13 (richin13/asdf-neovim)
• @particledecay (particledecay/asdf-osctl)
• @odarriba (odarriba/asdf-php)
• @code-lever (code-lever/asdf-rust)
• @mtatheonly (mtatheonly/asdf-scala)
• @RykHawthorn (RykHawthorn/asdf-tflint)
• @ndac-todoroki (ndac-todoroki/asdf-v)

Unfortunately all mongodb plugins are broken.

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
Add the azure-cli plugin

Describe similar asdf features and why they are not sufficient
We already have gcloud and aws but we could also have azure

Describe workarounds you've considered
Manually install azure-cli in the machine

Additional context
N/A

https://puppet.com/download-open-source-puppet

https://buildah.io/

Is your feature request related to a problem? Please describe

It is not a problem. I just wanted to share the plugin I have created for `sccache' https://github.com/mozilla/sccache

Describe the proposed solution

The plugin is located at https://github.com/emersonmx/asdf-sccache.git

Describe similar asdf features and why they are not sufficient

none

Describe other workarounds you've considered

none

The naming of plugins has a bad inconsistency between platforms due to case sensitivity of the filesystem.

On OS X asdf plugin-add luajit works, but on a standard linux install asdf plugin-add luaJIT is requried. I suggest that plugins should all be a single case for consistency between platforms. Since the vast majority of the plugins are currently in lowercase, this should be the default and requirement of future plugins.

Recently I've become interested in flutter, and looking at the list, there is yet to be a plugin for it. Would it be possible to add one?

Thanks

We already have a Postgres plugin. We need a MySQL plugin. I'm not sure how difficult downloading and installing MySQL will be, but if it's possible it would be nice to have a plugin for it.

Python's Poetry: https://poetry.eustace.io/

both plugins,
Ksonnet and Kubecfg
have a link to Banno/asdf-ksonnet

I guess Kubecfg should have a different link?

A link to the plugin guide needs to be displayed in the section of the readme that covers adding plugins.

We also need to specify the standards for plugin inclusion. Plugins without automated test builds are not included, nor are those with failing builds.

We also need to say that any plugin that is added can be removed or replaced at any time for any reason. There are two reasons this may be necessary:

• It's quite probably we will have multiple plugins for the same programming language. One will likely be better maintained than the other.
• There could be a plugin containing malicious code.

While added PR #96 I found, that CI gave me red status, while my plugin is working.

It happening because of coupling all plugins in 1 bunch, and if even 1 fails - test fails.

But we do not control the plugins after PR merge, so we can not base on this criteria. It can be only warning, and test script should test only new plugin, and be red only while it is red.

Any thoughts?

Is your feature request related to a problem? Please describe

asdf does not have a spectral plugin

Describe the proposed solution

I have created a spectral plugin for asdf. I've created a PR (#644) to add it to this list.
vbyrd/asdf-spectral

Describe similar asdf features and why they are not sufficient

N/A

Describe other workarounds you've considered

N/A

I'm noticing that builds for this repo have only ever succeeded once -- in the commit that introduced them on October 18, 2017.

At this point, while I appreciate the intent, I think it's safe to say that after 19 months of consistent failure, the current strategy for Travis CI builds in this repo has proven to be... unfruitful. I mean, why bother with CI if we're just going to ignore the results, right?

So... let's think about what this repo is trying to achieve. From the README:

"...it's purpose is to serve a list of community maintained stable plugins"

Alright, so this helps us to frame a couple of questions:

1. How do we know if a plugin in the list is unstable?
2. What do we do if a plugin in the list is unstable?

The current Travis CI build does a reasonable job, I think, of answering 1 for us -- require that each plugin have a passing CI build.

Currently, as far as I can tell, nothing is happening for 2, and that's where it gets interesting.

1. If one is to strictly abide by the purpose defined in the README, if a plugin is unstable, it should not be presented in the list of plugins at all.
2. A slightly more lenient option may be to add a flag to asdf plugin-list-all to include/exclude unstable plugins (i.e: plugins whose builds are failing).
3. The most lenient option would be to do what is happening now: show all plugins, regardless of stability (passing/failing builds).

My problem with 1 is that users may be confused when/if plugins they expect to see no longer appear in the list, and it would not be clear to them where to go to investigate/troubleshoot.

My problem with 3 is that the Travis CI builds are meaningless. They're an unenforced policy, with no impact on the project's functionality or behavior.

Of these choices, my preference would be 2. Although it's more intrusive to asdf (i.e: potentially requires an upstream change to add the --include-unstable flag), it seems like a decent compromise between the extremes of options 1 (too strict) and 3 (too lenient).

Either way, having a Travis CI build on this repo contingent upon the passing status of every plugin is, in my opinion, not the optimal touch point to enforce plugin stability.

Thoughts? Ideas? I've love some feedback (and, really, validation from the repo maintainers) before starting down an implementation path that may turn out to be ill-conceived or against the grain.

https://gauge.org/

It would be nice to be able to have multiple versions of rabbitmq managed by asdf. I'm not sure how much trouble it will be to get a rabbitmq service running if rabbitmq is managed by asdf, but it should be possible.

Is your feature request related to a problem? Please describe

Hi

I created a plugin for https://github.com/twpayne/chezmoi. A program to manage dot files.

Describe the proposed solution

I will attach the pull request immediately.

Describe similar asdf features and why they are not sufficient

No plugin yet

Describe other workarounds you've considered

No plugin yet

Oracle has blocked unauthenticated downloads of modern builds of the JDK. They still provide unauthenticated access to some builds of JDK 8 and 7 that are a few years old, but this leaves users of more modern builds of JDK 8, 9, 10, 11 and 12 without an asdf option. The issue has been solved with an updated java plugin in PR #78 .