Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: [RTD-2580] log delete api key level increased to error #139

Merged
merged 1 commit into from
Jun 20, 2024

Conversation

lucaconsalvi
Copy link
Contributor

Description

List of Changes

Motivation and Context

How Has This Been Tested?

  • Unit Test Suite
  • Integration Test Suite
  • Api Tests
  • Load Tests

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

@lucaconsalvi lucaconsalvi requested a review from a team as a code owner June 18, 2024 11:34
Copy link

@@ -45,7 +45,7 @@
try {
authService.deleteAssociation(senderCode, internalId);
} catch (RecordNotFoundException e) {
log.warn("Failed to delete a non existing association by sendercode {}", senderCode);
log.error("Failed to delete a non existing association by sendercode {}", senderCode);

Check failure

Code scanning / CodeQL

Log Injection High

This log entry depends on a
user-provided value
.
@TommasoLencioni TommasoLencioni changed the title chore: [RTD-2580] log delete api key levvel increased to error chore: [RTD-2580] log delete api key level increased to error Jun 18, 2024
@lucaconsalvi lucaconsalvi merged commit ab50a15 into develop Jun 20, 2024
10 of 11 checks passed
@lucaconsalvi lucaconsalvi mentioned this pull request Jun 20, 2024
9 tasks
Copy link

🎉 This PR is included in version 1.1.6 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants