scaleway/action-scw

running action fails due to GH rate limit

Closed this issue · 0 comments

Using the action like instructed in the docs regularly results in the GH rate limit probably because some of the calls to their API are not using the secrets.GITHUB_TOKEN auth header.

The Scaleway support instructed me to add github-token: ${{ secrets.GITHUB_TOKEN }} which ofc did not work because it is not a supported config option.

Run scaleway/action-scw@be2696f261325a78354eda14988c80405f33e082
  with:
    export-config: true
    save-config: true
    access-key: ***
    secret-key: ***
    default-project-id: ***
    default-organization-id: ***
file:///home/runner/work/_actions/scaleway/action-scw/be2696f261325a78354eda14988c80405f33e082/dist/index.js:2451
                    const err = new HttpClientError(msg, statusCode);
                                ^

HttpClientError: API rate limit exceeded for 172.171.222.78. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)
    at HttpClient.<anonymous> (file:///home/runner/work/_actions/scaleway/action-scw/be2696f261325a78354eda14988c80405f33e082/dist/index.js:2451:33)
    at Generator.next (<anonymous>)
    at fulfilled (file:///home/runner/work/_actions/scaleway/action-scw/be2696f261325a78354eda14988c80405f33e082/dist/index.js:1841:58)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  statusCode: 403,
  result: {
    message: "API rate limit exceeded for 172.171.222.78. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
    documentation_url: 'https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting'
  }
}

Node.js v20.19.1