search

datawire / kubernaut

Instant ephemeral Kubernetes clusters for development and testing
Apache License 2.0
117 stars 8 forks source link

Upgrade to Scout 0.3.0, and have --query-only #22

Closed kflynn closed 6 years ago

kflynn commented 7 years ago

kubernaut kubeconfig --query-only won't output anything on success, and will use the exit code to indicate if you have a cluster claimed.

plombardi89 commented 7 years ago

I'm a little concerned with the --query-only option because it adds a new CLI design constraint I have to adhere to for future versions when I think there is a better mechanism for finding out if you have a cluster (e.g. I'd like to have kubernaut list-claims and kubernaut get-claim <name> return list of claims and details about a claim.

Is the only reason for this to avoid printing output? Is > /dev/null 2>&1 not good enough? What about the -p option? I'm curious what the use case was.