Improve the sensitive history scrubbing to allow retrieving token from az, gcloud, and kubectl#3641
Conversation
…m az, gcloud, and kubectl
andyleejordan
left a comment
There was a problem hiding this comment.
I'm ok with this but wary of the precedent it sets for us to get this right not only for these commands, but for every possible ask in the future. Like it's a nice improvement...but I could see this growing huge if we don't have a plan to decide which commands we don't scrub (and do scrub). Perhaps we should have a more general way to allow users to add exceptions?
The user can already add exceptions, or customized scrubbing by The improvement made to the default scrubbing algorithm is for general scenarios that many users will run into. Otherwise, we will ask the user to apply the |
|
🎉 |
PR Summary
Fix #3633
Improve the sensitive history scrubbing to allow retrieving token from
az,gcloud, andkubectl.The default sensitive history scrubbing was updated to handle retrieving token with gcloud, with Azure (both az cli and Az PowerShell), and with
kubectl(bothget secretanddescribe secret).PR Checklist
Microsoft Reviewers: Open in CodeFlow