Install via brew?

[deitch]

Can we make the packet cli available on Mac (and Linux) via homebrew? Also might want to think about Windows, where you can install via homebrew using WSL, or possibly Chocolatey.

[jacobsmith928]

@jasmingacic thoughts?

[jasmingacic]

It is doable, but before we'd have to set up a CI/CD pipeline so we can ensure that what we have is tested regularly.

[jacobsmith928]

Fully supportive of a CI/CD pipeline, could you coordinate with @deitch to align with what he has done for CCM and CSI?

[jasmingacic]

Hey @deitch should we get together and go over what @jacobsmith928 suggested?

[deitch]

Sounds good @jasmingacic . I am going to open a new issue just for CI, so we can keep the discussion focused and leave this one for brew.

[displague]

Now that goreleaser is being used on each tagged release through GitHub Workflows, this is more attainable:
https://goreleaser.com/customization/homebrew/

[idvoretskyi]

Any updates on this? :)

[displague]

@idvoretskyi I created a brew tap, but I'll need to verify that this configuration works first.
equinix/homebrew-tap#1

The next step would be to update goreleaser in this project to update the tap on each release.

[crayzeigh]

Created a PR that should cause goreleaser to generate the brew formula into equinix/homebrew-tap on each release once committed that should at least solve the bare minimum requirements. Probably worth thinking about committing and maintaining in homebrew-core after we confirm this is working.

[displague]

I've created an issue to track a limitation that I encountered when setting up the secrets needed to publish to the tap.

In the meanwhile, I can grant the tap account access to metal-cli so that one token can update both projects.

[displague]

Noting here that it is also possible to install on FreeBSD via https://www.freshports.org/sysutils/equinix-metal-cli/ as noted in the README.md thanks to #249