Use GOPROXY to get latest releases instead of git APIs

[adilGhaffarDev]

Problem

Here:

metal3-dev-env/lib/releases.sh

Line 3 in 04b45cd

function get_latest_release() {

We are using git api to get the latest releases, if git API is used multiple times without GITHUB_TOKEN we start getting following error:

rate limit for github api has been reached. Please wait one hour or get a personal API token and assign it to the GITHUB_TOKEN environment variable

Solution

Instead of using git APIs we should use GOPROXY. In this way we will not need GITHUB_TOKEN and we will also get rid of rate limit error.

Below are GOPROXY links that list out all releases:

• CAPI: https://proxy.golang.org/sigs.k8s.io/cluster-api/@v/list
• CAPM3: https://proxy.golang.org/github.com/metal3-io/cluster-api-provider-metal3/@v/list

Write a function that get latest release from GOPROXY links and use that to get latest releases

/good-first-issue

[metal3-io-bot]

@adilGhaffarDev:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

Problem

Here:

metal3-dev-env/lib/releases.sh

Line 3 in 04b45cd

function get_latest_release() {

We are using git api to get the latest releases, if git API is used multiple times without GITHUB_TOKEN we start getting following error:

rate limit for github api has been reached. Please wait one hour or get a personal API token and assign it to the GITHUB_TOKEN environment variable

Solution:

Instead of using git APIs we should use GOPROXY. In this way we will not need GITHUB_TOKEN and we will also get rid of rate limit error.

Below are GOPROXY links that list out all releases:

• CAPI: https://proxy.golang.org/sigs.k8s.io/cluster-api/@v/list
• CAPM3: https://proxy.golang.org/github.com/metal3-io/cluster-api-provider-metal3/@v/list

/good-first-issue

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/test-infra repository.

[adilGhaffarDev]

/triage accepted

[metal3-io-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[Rozzii]

/remove-lifecycle stale

[Rozzii]

/remove-lifecycle stale