Closed LukeShu closed 2 years ago
Another approach is to check stdout for a tty and only show interactive stuff if it has one.
If it's called from a shell script, the script has no real reason to capture stdout, so kubernaut
's stdout would probably still be a tty, even if it's not being called interactively. The "solution" to which would be for the caller to pipe it to cat
, which is a real bad smell.
Kubernaut is dead.
Whenever you call
kubernaut claims create
it spits out a big usage message:This is surely helpful for interactive use. However, when calling it from another program/script, this is just noise that the user would have to ignore. I'm hesitant to just say
>/dev/null
because if there is diagnostic output, I don't want to hide it.I think that it would be a good UI improvement to either
-q
/--quiet
flag to silence that message, or