Custom asdf registry

[Sytten]

Hi!
I want to scale usage of mise in our organization, but one thing that is kinda problematic is the fact that asdf plugins cannot be audited first. Ideally I would like to create my own registry of approved plugins and they should be the only ones that can be installed. Maybe this could be implemented as a backend? (I am not too sure about the concepts).
Open to pitching in the implementation, but I feel this would be a good thing for organizations that want to manage their supply chain. Kinda similar to what Aqua calls a registry.
Thanks

[mrjk]

I am looking for the exact same feature. Is it possible to have that overridable somewhere ?

[jdx]

https://mise.jdx.dev/configuration.html#mise-shorthands-file-config-mise-shorthands-toml

[mrjk]

Ok, thank you very much, I completely missed that one! 👍

[NiklasRosenstein]

I think I'm trying to do the same as @mrjk, but I don't fully understand how the config docs help in that.

Basically, I'd like that I can have my own, separate GitHub repository that acts similar to let's say an aqua registry (i.e. has a registry.yaml file) and that I can install tools from it in addition to tools from the official mise registry(/ies).

The Plugins docs mention:

Historically it was the only way to add new tools (as the only backend was asdf).

[...] However, now with core tools and backends like aqua/ubi, plugins are no longer necessary to run most tools in mise

If you want to integrate a new tool into mise, you should either try to get it into the aqua registry or see if it can be installed with ubi. Then add it to the registry.

I only see two options if I don't want to go through contributing the tool to the mise registry:

1. Use a plugin instead (although I'm not sure how I would create a plugin that does not provide just a single tool, but a host of tools through an auqa registry.yaml)
2. Fork the mise registry to add my tool and set the aqua.registry_url option

Am I getting this right?

Although maybe I'm confusing some things because the option default is https://github.com/aquaproj/aqua-registry but there's also the mise registry.toml ... 😕

[iilyak]

The registry term is a bit overloaded. It could mean aqua registry or mise registry and possibly other things. I am very confused since it seems that original question was answered and people are able to use custom registry. Maybe I am trying to do something different? I want to specify this:

cat registry.yaml

❯ cat registry.yaml
packages:
  - name: lua/lua
    type: http
    repo_owner: Lua.org
    repo_name: lua
    url: https://www.lua.org/ftp/lua-{{trimV .Version}}.tar.gz
    description: Lua is a lightweight, high-level, multi-paradigm programming language
    format: tar.gz

Also my goal is to configure the registry for project so I don't use ~/.config/mise/config.toml file. Here is how I try to do it

cat

❯ cat mise.toml
[tools]
"aqua:lua" = 'latest'

[settings.aqua]
"registry_url" = "registry.yaml"

I got the following error

mise WARN  invalid aqua tool: lua
mise cloning aqua registry to "/Users/iilyak/Library/Caches/mise/aqua-registry"
mise WARN  git clone failed: unsupported URL protocol; class=Net (12)
error: '/Users/iilyak/Code/experiments/mise-test/registry.yaml' does not look like a v2 or v3 bundle file
fatal: invalid gitfile format: /Users/iilyak/Code/experiments/mise-test/registry.yaml
fatal: Could not read from remote repository.

I read it as registry_url has to point to real repository. How would I use a plane registry.yaml file? Is what I ask different from the discussion title (if so should I start a new discussion)?