brew/mac: Install the M1 rpk version on M1 macs

[rkruze]

Currently, the homebrew recipe only installs the intel version of rpk. It should pick the right rpk package depending on the architecture that it is being installed on.

[twmb]

@ivotron can this be done by @r-vasquez? Is this to be done in vtools?

[ivotron]

sure thing. this has te be done in github actions . this is the workflow that needs to be updated: https://github.com/redpanda-data/redpanda/blob/dev/.github/workflows/rpk-build.yml

[r-vasquez]

Related: #4851

[r-vasquez]

Current rpk-build already builds, sign, and release for M1 (darwin/arm64) however the redpanda homebrew tap only use the intel version: https://github.com/redpanda-data/homebrew-tap/blob/main/Formula/redpanda.rb#L4

I'll make the change there.

[r-vasquez]

Created: redpanda-data/homebrew-tap#1

[ivotron]

ideally this needs to be automated. once that patch goes in, I think subsequent releases will fail next time the pipeline runs. instead, we can add support for pushing multiple artifacts by tweaking the github action https://github.com/mislav/bump-homebrew-formula-action

[andrewhsu]

It seems bump-homebrew-formula-action does not have provisions to update multiple architectures within a formula (see mislav/bump-homebrew-formula-action#5).

As an alternative, we could build a universal macOS binary. this is essentially a fat binary that is the combined filesize of the amd64 and arm64 binaries (~11MB total).

Or, we could use (or create) a different github action to update the homebrew formula.

Another approach could be to submit the formula to homebrew-core and keep the source code download up-to-date upon redpanda releases and let homebrew team compile the binaries. If it is accepted, the homebrew team would create bottle of binaries on macOS x86_64 and ARM and on x86_64 Linux.