Description of problem:

Client Version: 4.5.0-0.nightly-2020-04-17-114625
Server Version: 4.5.0-0.nightly-2020-04-17-114625
Kubernetes Version: v1.18.0-rc.1
[root@rh8-tools ipi]# ./openshift-install version
./openshift-install 4.5.0-0.nightly-2020-04-17-114625
built from commit 19d22e67d372145f24bed3030aa049da9ebc398e
release image quay.io/openshift-release-dev/ocp-release-nightly@sha256:2357cbed27ba57912fc92392ef7cacb1a79546587946771ab6a71fbf397056a3


Nested folders in vSpheres via terraform are handled via a parent child relationship. See:

data "vsphere_datacenter" "dc" {}
resource "vsphere_folder" "parent" {
  path          = "terraform-test-parent"
  type          = "vm"
  datacenter_id = "${data.vsphere_datacenter.dc.id}"
}
resource "vsphere_folder" "folder" {
  path          = "${vsphere_folder.parent.path}/terraform-test-folder"
  type          = "vm"
  datacenter_id = "${data.vsphere_datacenter.dc.id}"
}

https://www.terraform.io/docs/providers/vsphere/r/folder.html

At the moment the installer creates only a single folder:
https://github.com/openshift/installer/blob/master/data/data/vsphere/main.tf#L68-L73

Steps to Reproduce:
1. Specify a nested folder in install-config e.g. /default-dc/vm/terraform-test-folder/ocp

2. Run installation VMs will be generated in ocp folder at root here: /default-dc/vm/

3. May additionally create issues with cloud provider


Expected results:
VMs created at /default-dc/vm/terraform-test-folder/ocp