Closed bflad closed 1 year ago
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.
If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!
I'm going to lock this issue because it has been closed for 30 days ā³. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
Description
Here is another static analysis item I had worked on some time ago, but for whatever reason never created an issue. The codebase strongly prefers naming the AWS Go SDK service clients in each of the Create/Read/Update/Delete functions as
conn
for consistency, e.g.There are a few lingering resources that use alternate naming styles that should be standardized. This handling will need file excludes (or code comments) for known cases where multiple clients are required, where typically the convention is then
{SERVICE}conn
.Potential Semgrep Rule
Current reports: