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

fix resource name #193

Merged
merged 1 commit into from
Sep 10, 2024
Merged

fix resource name #193

merged 1 commit into from
Sep 10, 2024

Conversation

dandersonsw
Copy link
Contributor

Changes proposed in this pull request:

  • Missed the word broker in the resource name when actually using it

Things to check

  • For any logging statements, is there any chance that they could be logging sensitive data?
  • Are log statements using a logging library with a logging level set? Setting a logging level means that log statements "below" that level will not be written to the output. For example, if the logging level is set to INFO and debugging statements are written with log.debug or similar, then they won't be written to the otput, which can prevent unintentional leaks of sensitive data.

Security considerations

Fixing the resource name

@dandersonsw dandersonsw requested a review from a team as a code owner September 10, 2024 15:12
@dandersonsw dandersonsw merged commit 09c62a9 into main Sep 10, 2024
1 check passed
@dandersonsw dandersonsw deleted the fix-resource-name branch September 10, 2024 15:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants