-
Notifications
You must be signed in to change notification settings - Fork 38
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(deps): migrate to the official Zeebe Spring SDK #3193
base: main
Are you sure you want to change the base?
Conversation
@@ -62,10 +59,10 @@ | |||
} | |||
|
|||
public Map<String, String> getSecrets() { | |||
LOGGER.debug("Loading secrets from " + secretsEndpoint); | |||
LOGGER.debug("Loading secrets from {}", secretsEndpoint); |
Check failure
Code scanning / CodeQL
Insertion of sensitive information into log files High
potentially sensitive information
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix AI 8 days ago
To fix the problem, we should avoid logging the secretsEndpoint
directly. Instead, we can log a generic message indicating that secrets are being loaded without revealing the endpoint. This approach maintains the logging functionality for debugging purposes without exposing potentially sensitive information.
- Modify the log message on line 62 to remove the
secretsEndpoint
. - Ensure the new log message still provides useful information for debugging without exposing sensitive details.
-
Copy modified line R62
@@ -61,3 +61,3 @@ | ||
public Map<String, String> getSecrets() { | ||
LOGGER.debug("Loading secrets from {}", secretsEndpoint); | ||
LOGGER.debug("Loading secrets from the configured endpoint."); | ||
try (CloseableHttpClient httpClient = HttpClientBuilder.create().build()) { |
9c1fc20
to
795af25
Compare
Description
This PR will migrate the Connectors project to the official Camunda Spring SDK. Until now, we have been using the community-supported library Spring Zeebe which is now on a deprecation path.
Key changes:
Related issues
closes #2896