Kralizek / Kralizek/AWSSecretsManagerConfigurationExtensions
Retry logic in credentials polling
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 260
- Forks
- 54
- Avg merge
- 5h 56m
- Merged PRs (30d)
- 5
Description
Is it worth considering retry logic in credential polling functionality if multiple microservices try to access the same secret value and due to rate limiting functionality code fails to retrieve the updated credentials?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the credential polling implementation and reviewing how AWS Secrets Manager rate-limit failures are surfaced. Clarify retry conditions, limits, and expected behavior before identifying the tests needed; the issue is done when the behavior is specified and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, csharp
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100