feat: retry IBM Cloud Global Catalog calls on HTTP 429#516
feat: retry IBM Cloud Global Catalog calls on HTTP 429#516nekkunti wants to merge 1 commit intokubernetes-sigs:mainfrom
Conversation
|
@meomnzak @pfeifferj can you look into this PR |
|
/ok-to-test |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #516 +/- ##
==========================================
+ Coverage 56.92% 57.00% +0.07%
==========================================
Files 61 62 +1
Lines 8992 9017 +25
==========================================
+ Hits 5119 5140 +21
- Misses 3508 3511 +3
- Partials 365 366 +1
🚀 New features to boost your workflow:
|
203581d to
d0fad40
Compare
|
/ok-to-test |
|
@nekkunti: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn 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. |
|
/ok-to-test |
|
@nekkunti: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn 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. |
|
@meomnzak. Could you check now |
|
/ok-to-test |
Add a shared DoWithRetry helper to handle IBM Cloud API rate limiting (HTTP 429) using exponential backoff and honoring the Retry-After header when present. Apply the retry wrapper to GlobalCatalog client call sites: - GetCatalogEntryWithContext - ListCatalogEntriesWithContext - GetPricing Add unit tests covering: - successful call without retry - non-429 passthrough - retry then success - retry exhaustion - context cancellation - Retry-After handling without real sleep - Retry InvalidRetryAfterFallsBack Signed-off-by: Anand Nekkunti <anand.nekkunti@ibm.com>
d0fad40 to
77795d6
Compare
|
/ok-to-test |
|
@nekkunti: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn 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. |
|
@meomnzak Could you check now, All comments are resolved |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: meomnzak, nekkunti The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Thank you. |
|
@meomnzak Could you trigger tests @meomnzak @pfeifferj Please approve this PR . |
|
/ok-to-test |
|
@nekkunti: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn 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. |
|
/ok-to-test |
|
@pfeifferj @meomnzak |
Description
Add a shared DoWithRetry helper to handle IBM Cloud API rate limiting (HTTP 429) using exponential backoff and honoring the Retry-After header when present.
Apply the retry wrapper to GlobalCatalog client call sites:
It fixes issue#502
Type of change
Testing