apptio / kube-config Goto Github PK

Cleaner way of making the configuration

Use goreleaser

#8 should be separated into a function as presently it's tucked away procedurally in the handleCallback function and erroneously exits (thinking was because we're done after it prints) and due to this exit clobbers the existing configuration.

So, if a user runs kube-config -g and previously had a working configuration for a particular tier, they will now have an empty file.

Objective

Refactor using cobra commands and flags to clearly and cleanly define verbs for kube-config. For a while, if not indefinitely, the no verb default should still generate a valid YAML and accept the --tier flag among others.

Proposal Ideas

Changes

• kube-config [login] (also default/null/no verb)
  • kube-config login [-t|--tier=<tier>] [-d|--debug] [-c|--cluster=<cluster>] [-n|namespace] [-o|--output=<file>] ...
• kube-config list
  • kube-config list tiers - list configured tiers
  • kube-config list groups - list remote AD groups
  • kube-config list config - prints config

Additions (New!)

• kube-config set
  • kube-config set cluster <cluster> [-n|--namespace=<namespace>] [-u|--username] - sets persistent defaults for cluster
  • kube-config set username <username> - sets default username
  • kube-config set configpath <directory> - sets default output dir