-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Don't write logs that contain environment variables #13877
Conversation
/ok-to-test |
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.
Nice.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sharifelgamal, spowelljr The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kvm2 driver with docker runtime
Times for minikube start: 54.9s 53.0s 52.9s 54.2s 55.2s Times for minikube ingress: 29.1s 30.1s 26.2s 30.1s 30.2s docker driver with docker runtime |
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
Fixes #13527
The debug logging is very verbose and can sometimes contains logs that output every environment variable on the users computer. This in itself is not an issue, but if the user is to upload their logs to GitHub for debugging purposes they could have secrets or other sensitive tokens in their environment variables which shouldn't be exposed to the public.
This fix skips writing logs that contain all the environment variables to protect the user.
Before:
After: