Install packages by cargo or go_install if the asset for the platform isn't released in GitHub Releases

[suzuki-shunsuke]

Feature Overview

Install packages by cargo or go_install if the asset for the platform isn't released in GitHub Releases.

Why is the feature needed?

To support platforms where a tool doesn't provide assets.

For example, some github_release packages don't support linux/arm64 and windows.

Of course we can achieve this using overrides.

e.g. https://github.com/aquaproj/aqua-registry/blob/8d552f251ded112b42e681279d71b0af59fce85f/pkgs/slsa-framework/slsa-verifier/registry.yaml#L11-L19

        type: go_install
        path: github.com/slsa-framework/slsa-verifier/v2/cli/slsa-verifier
        asset: slsa-verifier
        overrides:
          - goos: linux
            goarch: amd64
            type: github_release
            asset: slsa-verifier-{{.OS}}-{{.Arch}}
            format: raw

But I'd like to provide the simple way to achieve this.

Does the feature include Breaking Changes?

No.

Example Code

registry.yaml

        type: github_release
        asset: slsa-verifier-{{.OS}}-{{.Arch}}
        format: raw
        supported_envs:
          - linux/amd64
        go_path: github.com/slsa-framework/slsa-verifier/v2/cli/slsa-verifier # New!

If the platform isn't contained in supported_envs and go_path is set, the package is installed by go_install.

Reference

• https://twitter.com/wbelucky/status/1661279221874819073

[suzuki-shunsuke]

There are two issues.

1. Setting go_path to existing packages are bothersome 😅
2. templating major version in path

[sheldonhull]

With GOPATH, aren't you leaving that to the user? Ie, I have mine hardcoded to $HOME/go so that all the various tools, including devcontainers, vm's and more can all benefit from the consistent location.

When I use aqua managed go, that path is honored I believe isn't it? Ie, if I do a custom go install even though aqua proxy handles the bin path, the actual packages underneath are still all stored in my consistent location, right?

[suzuki-shunsuke]

Yeah, go_path is different from the environment variable GOPATH.
go_path is Go Module path such as github.com/slsa-framework/slsa-verifier/v2/cli/slsa-verifier.
aqua installs packages in AQUA_ROOT_DIR.

When you run go managed by aqua, aqua doesn't set any environment variables such as GOPATH, so they are up to you.

[suzuki-shunsuke]

I created a related discussion.

• https://github.com/orgs/aquaproj/discussions/2039

[suzuki-shunsuke]

Moved to #2132