[FEATURE REQUEST] Return more information when management api rate limit happen

Open
#1,836 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
api, cli

Research direction

No file or test is named. Start by locating the Fastly Management API 429 error handling in the CLI and inspect how Fastly-RateLimit-* response headers are received; done means the CLI's rate-limit error includes that header information while retaining the existing message.

Written by the indexing model from the issue text.

Description

feature request

Is your feature request related to a problem? Please describe.
We have hundreds of different services and when we in some operations batching changes over all of them we and up in that the Fastly Management API rate limit the requests and the CLI returns ERROR: the Fastly API returned 429 Too Many Requests: You have exceeded your hourly rate limit. Please contact support@fastly.com if you think this is a mistake..

The rate limit's are described on https://www.fastly.com/documentation/reference/api/#rate-limiting

Describe the solution you'd like
The error message is clear and consist but should like to have more information in the error message, like the information from the Fastly-RateLimit-* headers. I think the Fastly CLI just return the information message.

Dominant language
Go
Stars
164
Forks
80
Avg merge
14h 22m
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

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.

More from fastly/cli

All issues in fastly/cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.