Log attempts to output resp.Body #104184
Comments
@SergeyKanzhelev: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/help |
@SergeyKanzhelev: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
FYI, |
/assign |
Hi, @feeltimeQ I just found a place to test my first submit. If you are still working on this, please let me know. I'll close my PR |
Hi, @skywe-tang, l still working on this issues, thanks . |
OK, go ahead. This PR #104225 can be used as a reference, I‘ll close it |
What happened:
Log messages like
body of failing http response: &{0x531900 0xc0010d2780 0x775180}
are not very informative./sig cloud-provider
What you expected to happen:
Either actual response body or none of it if this is a security concern.
/sig security
sig security to confirm it is ok to change this to log an actual response body.
How to reproduce it (as minimally and precisely as possible):
two places it is being logged:
kubernetes/staging/src/k8s.io/legacy-cloud-providers/gce/gcpcredential/credentialutil.go
Line 63 in ea07644
kubernetes/pkg/credentialprovider/config.go
Line 206 in ea07644
Environment:
kubectl version
):1.20, but doesn't mattercat /etc/os-release
):COSThe text was updated successfully, but these errors were encountered: