jbox-web aqua registry

A custom aqua registry that replicates the vfox-* mise plugins published under the jbox-web org. It defines 32 CLI tools (observability/infra binaries plus jbox-web internal tools) as aqua github_release / http packages, with the same binaries, checksum verification, and platform coverage the vfox plugins provided.

The root registry.yaml is generated — see Maintaining the registry before touching anything under pkgs/.

The real consumer is mise's aqua backend, not aqua itself. Point mise at this repository via aqua.registries and it will check our registry.yaml before the baked-in official aqua registry.

Declarative (mise.toml):

[settings]
aqua.registries = ["https://github.com/jbox-web/aqua-registry"]

[tools]
"aqua:prometheus/prometheus" = "3.5.1"

Imperative:

MISE_AQUA_REGISTRIES=https://github.com/jbox-web/aqua-registry mise use -g aqua:prometheus/prometheus@3.5.1

Under the hood mise downloads the root registry.yaml from this repo and resolves aqua:<owner>/<repo> references against it before falling back to the official registry baked into mise. This replaces the old vfox pattern:

# before (vfox plugin)
mise plugin install prometheus https://github.com/jbox-web/vfox-prometheus
mise use -g prometheus@3.5.1

# now (aqua backend, this registry)
mise use -g aqua:prometheus/prometheus@3.5.1

(Aqua-native consumption via a github_content registry entry in an aqua policy file is also possible, but it is not how jbox-web's Docker images use this repository.)

All references below are aqua:<repo_owner>/<repo_name> as declared in registry.yaml.

• composer (aqua:composer/composer) installs a PHP .phar, not a native binary. It installs fine through this registry, but running it (composer --version) requires a php runtime on PATH.
• openobserve (aqua:openobserve/openobserve) is a type: http package: upstream stopped publishing GitHub Releases, so binaries are fetched from downloads.openobserve.ai while available versions are still listed from GitHub tags.

• Package sources live one per upstream repo, under pkgs/<upstream-owner>/<upstream-repo>/registry.yaml.
• The root registry.yaml is generated by scripts/build-registry.sh from everything under pkgs/. Never hand-edit the root file — regenerate it after any change under pkgs/.
• Do not use aquaproj/registry-tool (argd) to scaffold or generate packages: it is built to contribute to the official aquaproj/aqua-registry and pulls in the entire upstream registry. Use aqua's own aqua gr <owner>/<repo> (prints a package template to stdout, no git operations) plus scripts/build-registry.sh instead.

Test a package against a freshly regenerated local registry without touching the published one:

MISE_AQUA_REGISTRIES="file://$PWD" MISE_AQUA_REGISTRY_CACHE_TTL=0 mise x "aqua:<repo>@<ver>" -- <cmd>