-
Notifications
You must be signed in to change notification settings - Fork 841
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
infra/gcp/prow: actually remove extraneous ssh-keys #1894
infra/gcp/prow: actually remove extraneous ssh-keys #1894
Conversation
0a0fef4
to
5d792b7
Compare
oh right, resetting ssh-keys means a different comparison needs to be used
5d792b7
to
37e374a
Compare
Running Twice, just to be sure the change takes. |
37e374a
to
9fb7975
Compare
Removed 37e374a |
/hold |
/hold cancel |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hasheddan, spiffxp 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 |
/lgtm |
I have added a [wip] commit to allow me to run
./infra/gcp/prow/ensure-e2e-projects.sh
with a manual edit that skips everything per-project except ssh-key editing. Once that's done, I'll drop the [wip] commit from this PR.The code as previously written didn't actually drop ssh-keys. It does now, by using a different comparison when
K8S_INFRA_ENSURE_E2E_PROJECTS_RESETS_SSH_KEYS
istrue
. To make it more obvious what's happening when editing ssh keys in project metadata, simulate a diff of before/after changes.