The Update Go version in vitess-operator step (pre-release) used to only update the Golang version used in vtop if vtop was behind by at least 1 golang major version. Since we recently changed vitess' go mod, we must be using the proper Golang version in vtop's test and docker images at all time to ensure that the tests are passing. This PR changes the mechanism and always make sure that both repositories are on the exact same Golang version, if not a PR is automatically created to update the Golang version of vtop.
In this PR I am also adding some code to change the Golang version in the buildkite pipeline, which was missed before.
The
Update Go version in vitess-operatorstep (pre-release) used to only update the Golang version used in vtop if vtop was behind by at least 1 golang major version. Since we recently changed vitess' go mod, we must be using the proper Golang version in vtop's test and docker images at all time to ensure that the tests are passing. This PR changes the mechanism and always make sure that both repositories are on the exact same Golang version, if not a PR is automatically created to update the Golang version of vtop.In this PR I am also adding some code to change the Golang version in the buildkite pipeline, which was missed before.
Testing:
https://github.com/frouioui/vitess/issues/364 is my testing release issue, and when running the step I end up with a new PR to update the Go version of my vtop: https://github.com/frouioui/vitess-operator/pull/26