gold file generation: emit kubectl stderr, so it's easier to debug #2998
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I was regenerating gold files as part of another PR, but all the gold file copies failed. This stops the gold file generator from hiding stderr, so it's easier to troubleshoot.
In my case, the problem is that gold file generation doesn't honor
DEV_KUBECONFIG, and auth was failing against the (different) cluster described in my normalKUBECONFIG. It feels like fixing that is as easy as addingKUBECONFIG=$DEV_KUBECONFIGto thekubectlinvocation here, but I wasn't sure if there were any other workflows that depend on the existing behavior.