fastly CLI support for ARM macOS ?

[yusukebe]

Version

Fastly CLI version 0.43.0 (7172a30)
Built with go version go1.17.2 linux/amd64

What happened

I have been installed fastly CLI by using homebrew tap command and tried to do fastly compute serve. Then the command threw the error message below:

ERROR: error downloading latest Viceroy release: no asset found for your OS (darwin) and architecture (arm64).

Does fastly CLI support for ARM macOS?

My environment is:

Darwin 21.1.0 arm64 arm

[Integralist]

Hi @yusukebe

Thanks for raising this issue.

The actual issue here is related to the viceroy binary (which is what is called to support the fastly compute serve feature) not having a corresponding release asset: https://github.com/fastly/Viceroy/releases/tag/v0.2.5

Looks like only AMD64 is being produced. I'll reach out to the Viceroy team about this.

[yusukebe]

Hi @Integralist

OK, I see. Thank you for your reply and creating the issue on fastly/Viceroy/issues project!

[voxpelli]

Any way to force it to use the AMD64 for now?

[Integralist]

Hi @voxpelli unfortunately there isn't at the moment.

There's a few ways we could side-step this issue...

1. Provide a flag to skip the logic to check viceroy is available (this will allow you to manually install AMD Viceroy).
2. Provide flags for setting the viceroy os/arch that the CLI is otherwise expecting.
3. Provide env vars to override the viceroy os/arch that the CLI is otherwise expecting.

I'll chat with my team about these options and any other workarounds while we wait for Viceroy to support ARM.

[voxpelli]

I think I can compile Viceroy myself and it should find it locally if it's in my path, right?

[voxpelli]

I double checked and did cargo install viceroy and viceroy --version now I get viceroy 0.2.5, yet the cli tool still tries to download it.

I'm sure this worked before when I installed it manually 🤔

[Integralist]

The CLI will try to install or update the Viceroy asset that matches the CLI's own OS/Arch (e.g. it uses runtime.GOOS and runtime.GOARCH).

[Integralist]

yet the cli tool still tries to download it.

This will likely be because the CLI installs the Viceroy binary into either os.UserConfigDir or os.UserHomeDir and so the cargo install viceroy is likely placing the binary in a different directory.

[voxpelli]

Right, would it be possible to at least optionally have it use whatever compatible one that’s in my PATH?

[Integralist]

Yup, that's definitely another option. Lookup in ConfigDir then HomeDir and failing that try the standard os.LookPath

[thiagopnts]

in the meantime this is how I'm getting it to work(assuming viceroy is installed and in your PATH)

ln -s $(which viceroy) $HOME/Library/Application\ Support/fastly/viceroy