IBM-Cloud / IBM-Cloud/ibm-cloud-cli-release

ibmcloud rate limit support - feature request

Open
#60 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
160
Forks
74
PR merge metrics
No merged PRs in 30d

Description

Hi there,

We have a bash script to run the 'ibmcloud' command several times in order to set up our IBM Cloud stuff.

Sometimes we are getting an error from the API server (status code 429) related to the rate limits.

FAILED
Error response from server. Status code: 429; description: The request frequency from this IP exceeded the allowable rate of 30 per 60000 ms with a minimum separation of 0 ms. Please check the 'X-RateLimit-Limit', and 'X-RateLimit-Reset' header values returned by the server..

Is it planned to add support for this in the upcoming releases of the ibmcloud cli? In this way, the ibmcloud manage the 429 status code, wait a while and re-attempt again X times.

It would be very interesting to have this support natively in the command line.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue describes a bash script invoking the ibmcloud command and receiving HTTP 429 responses from the IBM Cloud API. Start by locating the CLI's API request and error-handling entry points, then determine how rate-limit headers and retry counts should be handled; done means repeated commands recover from 429 responses without failing prematurely.

Written by the indexing model from the issue text.

Assessment

Tech stack
bash
Domain
cli, cloud
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.