The library DOS itself if logs:DescribeLogGroups permissions is not set
- Dominant language
- C#
- Stars
- 307
- Forks
- 135
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 4
Description
### Describe the bug
If the logs:DescribeLogGroups is not set, the library spams some api call. Could you please fix this, it should not do this just because the permission is not set.
Somewhat related is that it spams a log file if any error occurs (causing the computer to run out of disk space) . Again, this should not be happening.
Seems there are systemic issues with this library relating to not handling errors gracefully (correctly).
I guess I will just have to fix it myself, which I will do soon when I have time.
### Regression Issue
- [ ] Select this option if this issue appears to be a regression.
### Expected Behavior
No spam
### Current Behavior
Spam
### Reproduction Steps
Do not set logs:DescribeLogGroups
### Possible Solution
_No response_
### Additional Information/Context
_No response_
### AWS .NET SDK and/or Package version used
Latest
### Targeted .NET Platform
.net 8
### Operating System and version
Ecs
Contributor guide
Research direction
Start by reproducing the issue in an ECS environment without logs:DescribeLogGroups permission, as described in the issue. Trace the repeated API calls and error logging, then verify that missing permissions and other errors no longer cause request or log-file spam.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, csharp
- Domain
- cloud, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100