refactor(config): only require file argument

[jbrockopp]

No description provided.

[codecov]

Codecov Report

Merging #27 into master will decrease coverage by 0.89%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master      #27     +/-   ##
=========================================
- Coverage   51.35%   50.45%   -0.9%     
=========================================
  Files           8        8             
  Lines         333      327      -6     
=========================================
- Hits          171      165      -6     
  Misses        161      161             
  Partials        1        1

Impacted Files	Coverage Δ
cmd/vela-kubernetes/config.go	100% <ø> (ø)	⬆️

[meinenec]

Is config file enough or should this be config file or the other checks?

[jbrockopp]

@meinenec I believe the config file is enough by itself 👍 I'll elaborate a little further!

Here is a sample of a config file:

apiVersion: v1
kind: Config
preferences: {}

clusters:
- cluster:
    server:  <server>
  name: <cluster>

users:
- name: <user>
  user:
    token: <token>

contexts:
- context:
    cluster: <cluster>
    namespace: <namespace>
    user: <user>
  name: <content>
current-context: <context>

This file still works because the context, cluster etc. have already been set in that file 👍

The reason why we've added (and plan to add more) specific attributes to override the defaults set in the file (i.e. context, cluster etc.) is I'm assuming that some users of this plugin might have a config file with multiple objects already defined.

To which, they might like to customize which ones they're attempting to communicate with further beyond the current-context set in the config 😄

Eventually, I hope we can support the ability where we don't need to provide a file at all and can use this plugin with providing each attribute individually 🎉