Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle kubeconfig contents or path in provider #1255

Merged
merged 3 commits into from
Aug 17, 2020
Merged

Handle kubeconfig contents or path in provider #1255

merged 3 commits into from
Aug 17, 2020

Commits on Aug 17, 2020

  1. Handle kubeconfig contents or path in provider 

    Previously, we only handled the contents of a kubeconfig
as configuration for the k8s provivder. This change now
additionally supports passing in the path to a kubeconfig.
An error is only returned if both of these options fail to
load a valid k8s configuration.
    @lblackstone
    lblackstone committed Aug 17, 2020
    Configuration menu
    Copy the full SHA
    8002306 View commit details
    Browse the repository at this point in the history

  2. Handle literal '~' character

    @lblackstone
    lblackstone committed Aug 17, 2020
    Configuration menu
    Copy the full SHA
    8c78c88 View commit details
    Browse the repository at this point in the history

  3. Try bumping test deps

    @lblackstone
    lblackstone committed Aug 17, 2020
    Configuration menu
    Copy the full SHA
    1495af8 View commit details
    Browse the repository at this point in the history