Ryan Richard ca80d87dcf

Use rest.Config for discovery URL instead of env var ...

- Why? Because the discovery URL is already there in the kubeconfig; let's
  not make our lives more complicated by passing it in via an env var.
- Also allow for ytt callers to not specify data.values.discovery_url - there
  are going to be a non-trivial number of installers of placeholder-name
  that want to use the server URL found in the cluster-info ConfigMap.

Signed-off-by: Andrew Keesler <akeesler@vmware.com>

2020-08-03 14:36:08 -04:00

..

api_discovery_test.go

Resolve SingularName TODO with comment

2020-08-03 10:29:59 -04:00

client_test.go

Allow override of discovery URL via ConfigMap

2020-08-03 10:17:11 -04:00

deployment_test.go

Allow override of discovery URL via ConfigMap

2020-08-03 10:17:11 -04:00

kubectl_test.go

TestGetNodes prints more output for debugging failures

2020-07-08 16:37:25 -07:00

logindiscoveryconfig_test.go

Use rest.Config for discovery URL instead of env var

2020-08-03 14:36:08 -04:00

loginrequest_test.go

Allow override of discovery URL via ConfigMap

2020-08-03 10:17:11 -04:00

main_test.go

Change the name of the env var that turns on integration tests

2020-07-09 13:43:30 -07:00