-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🌱 Get latest releases with GOPROXY #1474
base: main
Are you sure you want to change the base?
🌱 Get latest releases with GOPROXY #1474
Conversation
bb5b113
to
d524294
Compare
d524294
to
6f2842f
Compare
/retitle 🌱 Get latest releases with GOPROXY |
b46edb8
to
6e17ded
Compare
/test metal3-centos-e2e-integration-test-release-1-8 |
6e17ded
to
af1aefc
Compare
03_launch_mgmt_cluster.sh
Outdated
@@ -10,6 +10,7 @@ source lib/releases.sh | |||
# shellcheck disable=SC1091 | |||
source lib/network.sh | |||
|
|||
export CAPI_CONFIG_FOLDER="${HOME}/.cluster-api" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
according to this condition https://github.com/metal3-io/metal3-dev-env/pull/1474/files#diff-417b79700310fc30a2ae54bd699206962d6a97cfe30018a66ba6854312acdf9dL114
CAPI_CONFIG_FOLDER should be set like this:
# Default CAPI_CONFIG_FOLDER to $HOME/.config folder if XDG_CONFIG_HOME not set
CONFIG_FOLDER="${XDG_CONFIG_HOME:-$HOME/.config}"
export CAPI_CONFIG_FOLDER="${CONFIG_FOLDER}/cluster-api"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Much better. We can have it like this, most of the cruft is gone. Lets fix bash syntax on the touched lines, and merge.
2f2d921
to
71d3b8a
Compare
/test metal3-centos-e2e-integration-test-release-1-8 |
Signed-off-by: peppi-lotta <[email protected]>
71d3b8a
to
638627d
Compare
/test metal3-centos-e2e-integration-test-release-1-8 |
/lgtm |
@adilGhaffarDev: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tuminoid The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@@ -10,6 +10,9 @@ source lib/releases.sh | |||
# shellcheck disable=SC1091 | |||
source lib/network.sh | |||
|
|||
# Default CAPI_CONFIG_FOLDER to $HOME/.config folder if XDG_CONFIG_HOME not set | |||
CONFIG_FOLDER="${XDG_CONFIG_HOME:-$HOME/.config}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: "directory" is a more common word in the Linux world
# 1.6.99 points to the head of the release-1.6 branch. Local override for CAPM3 is created for this version. | ||
export CAPM3RELEASE="v1.6.99" | ||
export CAPIRELEASE="${CAPIRELEASE:-$(get_latest_release "${CAPIRELEASEPATH}" "v1.6.")}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: would be great to avoid duplication by setting e.g. CAPI_RELEASE_PREFIX="v1.6." and then only setting CAPIRELEASE once after the "if" block
# exclude some versions. | ||
# Example usage: | ||
# get_latest_release_from_goproxy "https://proxy.golang.org/sigs.k8s.io/cluster-api/@v/list" "v1.8." "beta|rc|pre|alpha" | ||
get_latest_release_from_goproxy() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does not look like get_latest_release is used anywhere else, so you can probably replace the old function instead of creating a new one with a new name
Github hits rate limit when getting the latest release version. If go proxy is used instead of github api this problem will go away.
fixes: #1376