Open bigon opened 1 month ago
You don't have to run the completion
command every time, only when the minikube version changes...
Mostly it is saved to a file during packaging, for instance how it is done in the brew formula for minikube?
You don't have to run the completion command every time, only when the minikube version changes...
Well the completion
command prints some (ba)sh code that needs to be evaluated by the shell isn't it?
The following is how I'm loading the completion code:
$ cat .bashrc |grep minik
source <(minikube completion bash)
Edit: Not using a package here, just d/l the binary
Right, but you can save the output to a file
What Happened?
Hello,
minikube seems to generate logs file in /tmp for each command that are run
For example, I run
minikube version
and I ends up with a file in/tmp
:/tmp/minikube_version_486aa15011e42ace60f28d9e74c31051228d0192_0.log
Same with
minikube completion bash
for example. This is a problem since the command is run every-time I'm opening a shellAttach the log file
log.txt
Operating System
Other
Driver
N/A