iwilltry42 91426eabd1 cmd: make config initialization more general ... - move viper initialization from k3d config file to separate util sub-package in cmd/ - use that new subpackage init function to leverage the config file in `k3d cluster delete` - cover that with an e2e test case		2021-09-06 17:44:38 +02:00
..
cluster	cmd: make config initialization more general	2021-09-06 17:44:38 +02:00
config	feat(logging): using new package containing logrus.Logger instead of global scope logrus (closes #583) (#699, @Shanduur)	2021-08-18 12:22:44 +02:00
debug	feat(logging): using new package containing logrus.Logger instead of global scope logrus (closes #583) (#699, @Shanduur)	2021-08-18 12:22:44 +02:00
image	[Enhancement] Network Magic (#721)	2021-08-30 14:59:12 +02:00
kubeconfig	feat(logging): using new package containing logrus.Logger instead of global scope logrus (closes #583) (#699, @Shanduur)	2021-08-18 12:22:44 +02:00
node	feat(logging): using new package containing logrus.Logger instead of global scope logrus (closes #583) (#699, @Shanduur)	2021-08-18 12:22:44 +02:00
registry	feat(logging): using new package containing logrus.Logger instead of global scope logrus (closes #583) (#699, @Shanduur)	2021-08-18 12:22:44 +02:00
util	cmd: make config initialization more general	2021-09-06 17:44:38 +02:00
root.go	feat(logging): using new package containing logrus.Logger instead of global scope logrus (closes #583) (#699, @Shanduur)	2021-08-18 12:22:44 +02:00