-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
56878: server: remove KeepRedactable logs rpc option r=andreimatei a=andreimatei This patch removes the KeepRedactable option from the Logs and LogFile RPCs. The option existed just for backwards compatibility with pre-20.2 clients. Even for such old clients, I don't think there's real consequences to removing this option. This patch retains the behvior of the option being set. The option, when coupled with the Redact=false option, made the RPCs keep the log entries exactly as they are in the log file - i.e. redactable, with sensistive data markers. With this patch, the logs returned by the RPCs are either redacted, or redactable. "Flattening" them (i.e. not redacting, but stripping the markers) is no longer an option. The Logs RPC is used by the AdminUI, which doesn't use either Redact or KeepRedactable - so, with this patch, the UI will show logs with markers in them. I think that's OK. The LogFile RPC is used by the cli getting a debug zip. Since 20.2, the client is setting KeepRedactable, and so nothing changes. Older clients will get log entries with markers in them. This change is motivated by the fact that I'd like to replace the LogFile RPC with a more efficient version that returns a raw file, not a proto-encoded list of log entries. In fact we already have that RPC in the form of GetFiles, which we may be able to use. This KeepRedactable option was in my way. Release note: None Co-authored-by: Andrei Matei <[email protected]>
- Loading branch information
Showing
7 changed files
with
517 additions
and
642 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters