Ensure reauthenticate calls exec again #307
Merged
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.
KubeAuth.server
was being used to store both the user specifiedurl
kwarg and also the url loaded from the kube config.When loading the kubeconfig we check that the server hasn't been set because we don't want to overwrite a url set by the user. However after the first authentication from kubeconfig that attribute is set, so when we call reauthenticate it looks like a user has specified the url and we never refresh it, so we aren't actually reauthenticating at all.
This PR creates a new
_url
attribute to store the user specified url which allows us to differentiate between them.Updated a couple of tests to ensure that a user specified URL doesn't get overwritten, but a kubectl specified url (and other attributes) get reloaded when we reauthenticate.
Closes #306