-
Notifications
You must be signed in to change notification settings - Fork 41.5k
Second attempt at GCE tokens behavior to new format #13594
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
Conversation
@cjcullen I'm attempting to guard this on the environment variables passed in, so that we don't have the breakage in CI that we were expecting/got last night. |
GCE e2e build/test passed for commit 219a1fa. |
Labelling this PR as size/S |
I don't think we need to version guard this. That introduces extra cruft that we will immediately want to take out. Let's just manage the coordination a little better :). |
(And by let's, I mostly mean that I shouldn't have left the LGTM on overnight) |
@cjcullen Ack. |
GCE e2e build/test passed for commit 5936d0fb181048596cea0967e53efa12711fe971. |
GCE e2e build/test passed for commit 219a1fa. |
LGTM. |
Second attempt at GCE tokens behavior to new format
…3594-upstream-release-1.0 Automated cherry pick of #13594
Round two of #13449.