Own Aqua Registry

[gbloquel]

I am trying to create my own Aqua registry using the environment variable MISE_AQUA_REGISTRY_URL as described in the Aqua backend documentation.

In my registry, I have correctly followed the pkgs directory structure. Here is an example with k9s:

├── pkgs
│   └── derailed
│       └── k9s
│           ├── pkg.yaml
│           └── registry.yaml

This setup works, and I am able to install k9s successfully. However, I am confused by the fact that we do not have control over the registry.toml file, which lists what is installable. Perhaps this file should be generated dynamically based on what is exposed in the registry ?

I expected to see only the tools present in my Aqua registry when I run the mise registry command.

Here is what I currently see:

# All backends are disabled except for aqua
mise doctor
....
env_vars:
 
  MISE_AQUA_REGISTRY_URL=<OWN_AQUA_REGISTRY>

settings:
  disable_backends            ["asdf", "cargo", "core", "go", "npm", "pipx", "spm", "ubi", "vfox"] ~/.config/mise/config.toml
...

mise registry
Tool                          Backends
1password                     aqua:1password/cli
1password-cli                 aqua:1password/cli
act                           aqua:nektos/act
action-validator              aqua:mpalmer/action-validator
....
k9s                           aqua:derailed/k9s
...

Here is what I would like to see, so that my registry matches what is actually available in my own Aqua registry:

mise registry
Tool                          Backends
k9s                           aqua:derailed/k9s

I also tested the MISE_DISABLE_DEFAULT_REGISTRY variable, but it seems to only disable the default registry for the ASDF and VFOX backends, as per my understanding of the code here: shorthand.js. Perhaps the documentation could be clarified on this point.

What is the best way to use our own Aqua registry?

[gbloquel]

Hi @jdx,

I have provided you a PR to clarify the documentation you have integrated.

However, I might also be able to help with the implementation of the issue mentioned above using the Aqua backends. I just need to know if this is a bug and what solution you propose!