Closed karuppiah7890 closed 2 years ago
I think the error in the check is happening in the kube config backup stage not sure though https://github.com/vmware-tanzu/homebrew-tanzu/runs/5674398679?check_suite_focus=true#step:3:445
cc @dvonthenen @seemiller to check this out!
thanks!
Going forward, can we think about how we can avoid the duplication in TCE repo install script and the TCE formula code? Or at least have some way to ensure that when we change the install script (bash, bat) then we also make changes in the Homebrew formula and the Chocolatey install and uninstall scripts, as it's all related, so, whoever makes these changes will have context and will be able to make the atomic change of modifying the installation / uninstallation logic in all places - standalone install scripts, homebrew and chocolatey package code
cc @joshrosso @dvonthenen @stmcginnis
Going forward, can we think about how we can avoid the duplication in TCE repo install script and the TCE formula code? Or at least have some way to ensure that when we change the install script (bash, bat) then we also make changes in the Homebrew formula and the Chocolatey install and uninstall scripts, as it's all related, so, whoever makes these changes will have context and will be able to make the atomic change of modifying the installation / uninstallation logic in all places - standalone install scripts, homebrew and chocolatey package code
cc @joshrosso @dvonthenen @stmcginnis
The goal of the each of them are slightly different which is why they are separate currently. Install shouldn't be a problem and is probably the same. Uninstall there could be opportunity to consolidate, but there is also mention of UI based install which we should coordinate with.
The uninstall.sh/.bat is really meant for developers who are looking to completely delete everything from their system.
For end users, this is undesirable. There is some configuration we want to leave around in case we do an uninstall and then reinstall. We don't want to blow away things like the downloaded BOM and k8s configs.
@dvonthenen Shall we make the changes in #28 PR in this PR itself? We don't need to merge two PRs, however we can't merge formula for RC.2 , that would be weird, though we might immediately merge the other PR #28 in which case users will get only the latest Homebrew tap git repo after that point
@dvonthenen Shall we make the changes in #28 PR in this PR itself? We don't need to merge two PRs, however we can't merge formula for RC.2 , that would be weird, though we might immediately merge the other PR #28 in which case users will get only the latest Homebrew tap git repo after that point
If you want to include the changes for PR 28 in this one, it shouldn't really matter. We could merge 2 PRs or just 1. If you want to include, I can close the other PR and this should be done ASAP since we are releasing at 6am tomorrow.
On your other point, I'm not sure I understand the other part of your comment. We shouldn't allow users to access rc2 or any other pre-release (alpha, beta or rc) though homebrew (or choco). The end users should only be able to install final GA releases.
On your other point, I'm not sure I understand the other part of your comment. We shouldn't allow users to access rc2 or any other pre-release (alpha, beta or rc) though homebrew (or choco). The end users should only be able to install final GA releases.
Yeah, that's why I was wondering - why put two commits from two PRs, with one commit point to RC.2
If you want to include the changes for PR 28 in this one, it shouldn't really matter. We could merge 2 PRs or just 1. If you want to include, I can close the other PR and this should be done ASAP since we are releasing at 6am tomorrow.
Done π π
What this PR does / why we need it
Updates Homebrew formula for
v0.11.0
releasePending things to check by us
Which issue(s) this PR fixes
Fixes #26
Describe testing done for PR
On Linux -
On Mac -
Special notes for your reviewer
Questions
This PR currently uses the version as
v0.11.0-rc.2
and it's respective SHA sum for Linux and MacOS tar balls, which we need to update before merging the PRWe need to merge this PR only after we release
v0.11.0
Things that the reviewer needs to check