-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
backupccl: stop logging unsanitized backup stmt in schedule executor #99150
backupccl: stop logging unsanitized backup stmt in schedule executor #99150
Conversation
Informs cockroachdb#99145 Release note: None
It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR? 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Thanks for fixing this up.
If we wanted to go a bit further, we have some code in this file for creating redacted backup statements. We could print a redacted backup statement rather than just the schedule ID if we saw value in having the whole statement.
But, I personally thing that just the ID is fine.
bors r=stevendanna |
Build failed: |
bors r=retry |
Build failed (retrying...): |
bors r- |
Canceled. |
This patch ensures that no unsanitized uris or secret keys get written to the jobs table if the backup fails. Informs cockroachdb#99145 Release note: None
bors r=stevendanna |
Build succeeded: |
Informs #99145
Release note: None