Releases contain identical binary with 2 different names #5056
Labels
area/clusterawsadm
Issues or PRs related to clusterawsadm
area/ux
Issues or PRs related to UX
kind/bug
Categorizes issue or PR as related to a bug.
needs-priority
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
/kind bug
What steps did you take and what happened:
Starting with v2.4.2, we built binaries with the
.goreleaser.yaml
settings. This includes bothclusterctl-aws
andclusterawsadm
, which are the same binary, just different names.The clusterctl plugin docs state:
Under our current naming scheme, the user will have to rename the binary to use it since we include the OS and platform in the filename.
However, all of our documentation and the Cluster API book rely on the
clusterawsadm
name, and this has broken in the past.What did you expect to happen:
The client-side executable is built and included in a release only once. We need to come to consensus on what the name should be.
Anything else you would like to add:
Also of note, we provide instructions to
brew install clusterawsadm
.There was a Slack discussion about this topic that I've tried to summarize in this issue.
The text was updated successfully, but these errors were encountered: