Skip to content
This repository has been archived by the owner on Jan 9, 2020. It is now read-only.

Parse results of minikube status more rigorously #97

Merged

Conversation

ash211
Copy link

@ash211 ash211 commented Feb 10, 2017

Fixes #96

Prior code assumes the minikubeVM status line is always the first row output
from minikube status, and it is not when the version upgrade notifier prints
an upgrade suggestion message.

Prior code assumes the minikubeVM status line is always the first row output
from minikube status, and it is not when the version upgrade notifier prints
an upgrade suggestion message.
@kimoonkim
Copy link
Member

+1. I was puzzled by the version update notifier message a few times.

@mccheah
Copy link

mccheah commented Feb 11, 2017

It would be nice to filter the update notification everywhere. For example, it still prints when you run minikube ip or minikube start.

Alternatively, getting Minikube to point to the config.json which has the appropriate notification flag turned off would be ideal. Then we can skip this check entirely.

@ash211 ash211 force-pushed the fix/minikube-version-notifier branch from 3c89196 to c40953a Compare February 13, 2017 17:31
@ash211
Copy link
Author

ash211 commented Feb 13, 2017

@mccheah I added a filter for minikube ip since that can break the output parsing, but didn't do anything for minkube start since unexpected output there wouldn't break anything.

I'd rather not invest too much in fixing minikube since my personal belief is that we should support running tests against any k8s serverapi, not just minikube.

@mccheah
Copy link

mccheah commented Feb 13, 2017

Looks fine - will merge.

@mccheah mccheah merged commit d47c4d7 into k8s-support-alternate-incremental Feb 13, 2017
@mccheah mccheah deleted the fix/minikube-version-notifier branch February 13, 2017 23:18
ash211 added a commit that referenced this pull request Mar 8, 2017
* Parse results of minikube status more rigorously

Prior code assumes the minikubeVM status line is always the first row output
from minikube status, and it is not when the version upgrade notifier prints
an upgrade suggestion message.

* Also filter ip response to expected rows
foxish pushed a commit that referenced this pull request Jul 24, 2017
* Parse results of minikube status more rigorously

Prior code assumes the minikubeVM status line is always the first row output
from minikube status, and it is not when the version upgrade notifier prints
an upgrade suggestion message.

* Also filter ip response to expected rows
ifilonenko pushed a commit to ifilonenko/spark that referenced this pull request Feb 25, 2019
ifilonenko pushed a commit to ifilonenko/spark that referenced this pull request Feb 25, 2019
)

* Parse results of minikube status more rigorously

Prior code assumes the minikubeVM status line is always the first row output
from minikube status, and it is not when the version upgrade notifier prints
an upgrade suggestion message.

* Also filter ip response to expected rows
puneetloya pushed a commit to puneetloya/spark that referenced this pull request Mar 11, 2019
)

* Parse results of minikube status more rigorously

Prior code assumes the minikubeVM status line is always the first row output
from minikube status, and it is not when the version upgrade notifier prints
an upgrade suggestion message.

* Also filter ip response to expected rows
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants