tanzu-framework
tanzu-framework copied to clipboard
vmware-tanzu
Distribute the CLI binary through package managers
Describe the feature request
Currently, the process for installing the CLI is a little cumbersome. Consumers can work around this, but that's not ideal.
It would be better to distribute the core of the CLI through package managers (including support for things like homebrew, rpm, and deb).
Especially when combined with #2, this seems to allow for a much smoother user experience: install the CLI, login to a cluster, everything auto-magically appears.
Describe alternatives you've considered
One alternative would be to have a standard install.sh-style pattern that all consumers can rely on.
Affected product area (please put an X in all that apply)
- [ ] APIs
- [ ] Addons
- [x] CLI
- [ ] Docs
- [x] Installation
- [ ] Plugin
- [ ] Security
- [ ] Test and Release
- [ ] User Experience
Additional context
It would be better to distribute the core of the CLI through package managers (including support for things like homebrew, rpm, and deb).
Full support, we were planning to tackle this right when we open source TCE.
question: What would we expect brew install tanzu to install? Just the CLI with tanuz-framework plugins? TCE? From a community UX, I'd advocate it installs TCE, but this seems like an important conversation for PM and tech leads.
:+1: It might be nice to have both brew install tanzu and brew install tanzu-ce (or something like that).
Ideally, I think we'd just distribute the core CLI binary and use API-driven discovery of the relevant CLI plugins (#74) based on the cluster it was being used with.
brew build script? @marckhouzam
@heyjcollins So Brew works differently: it needs a formula as part of a dedicated git repository. The solution is currently available in my fork and will be made official once we have a release to make public. You can see the details here: https://github.com/marckhouzam/homebrew-tanzu/pull/1
