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
Update redacting functionality to redact all sensitive info in config when printing with view #109189
Update redacting functionality to redact all sensitive info in config when printing with view #109189
Conversation
Hi @mpuckett159. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
You'll notice in the above examples that |
/remove-sig api-machinery |
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 the PR @mpuckett159 !
/ok-to-test |
/remove-sig api-machinery |
ad84892
to
8c54589
Compare
/retest-required |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
752612d
to
8d84ad6
Compare
Sorry for the churn there, not exactly sure what I was thinking there 🙄 |
/test unit |
@soltysh: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
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. |
/test pull-kubernetes-unit |
8d84ad6
to
5a578aa
Compare
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.
/lgtm
/approve
/label tide/merge-method-squash
// client-certificate-data: REDACTED | ||
// client-key-data: REDACTED | ||
// client-certificate-data: DATA+OMITTED | ||
// client-key-data: DATA+OMITTED |
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.
did this really change?
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.
and why
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.
This test is for the ShortenConfig() and MinifyConfig() functions. ShortenConfig used to perform the action of redacting the secrets, but no longer handles that process and instead only omits byte data.
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mpuckett159, soltysh, sttts 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 |
… when printing with view (kubernetes#109189) * Add RedactSecrets function * Move RedactSecrets method to existing RawBytesData case * Update TestRedactSecrets to use new pattern of os.CreateTemp()
What type of PR is this?
/kind feature
What this PR does / why we need it:
Updates redacting functionality of
kubectl config view
to properly redact all config keys with adatapolicy
tag. This is accomplished by introducing a new functionRedactSecrets
in client-go and then consuming it in kubectl.Example usages
No flags:
With --raw:
Which issue(s) this PR fixes:
Fixes kubernetes/kubectl#1193
Does this PR introduce a user-facing change?