kubevirt / web-ui-components / 1803

82%

push

travis-ci-com

Configure V2V via ConfigMap (#507)

* Configure V2V via ConfigMap

This patch removes dependency on v2v-specific SERVER_FLAGS with the motivation
to call this code from upstream openshift/console without the need to
modify the bridge-process there.

The V2V deployment is newly configured via "v2v-vmware" ConfigMap within
the "openshift" namespace.

Example:
```
oc apply -f - <<EOF
apiVersion: v1
kind: ConfigMap
metadata:
  namespace: openshift
  name: v2v-vmware
data:
  v2v-conversion-image: [V2V-CONVERSION-IMAGE]
  kubevirt-vmware-image: [KUBEVIRT-VMWARE-IMAGE]
  kubevirt-vmware-image-pull-policy: IfNotPresent
EOF
```

It is farther expected to have
- v2vvmware CRD deployed [1]
- the vddk-pvc created as before

The kubevirt-vmware deployment logic is recently expected to be extracted
to a new operator (which does not exist yet).

[1] oc apply -f https://raw.githubusercontent.com/kubevirt/web-ui-operator/master/build/kubevirt-web-ui-ansible/roles/kubevirt_web_ui/files/kubevirt_v1alpha1_v2vvmware_crd.yaml

* refactor: move v2v ConfigMap read one level up

1695 of 2261 branches covered (74.97%)

Branch coverage included in aggregate %.

4007 of 4650 relevant lines covered (86.17%)

107.51 hits per line