OCP 4.13 - IPI vSphere Folder and Resource Pool YAML Changes

In new 4.13 deployment I have noted that vSphere has added new stanza for "regions" and " generated-failure-domain" but not really a great deal of ducmentation about new foromat to help explain how to use, or to remediate cluster deployments to be in correct vSphere / vcnetetr : (VM) folders or Resource pools.

Ex: 4.10-4.12
platform:
vsphere:
apiVIP: 172.16.100.63
cluster: cluster
datacenter: datacenter
defaultDatastore: vsanDatastore
ingressVIP: 172.16.100.73
network: production_100
password: password
username: openshift@acme.local
vCenter: vcenter01.acme.local11/14/2022
folder: /datacenter/vm/demos/redhat/ocpdev

But new file cannot use: folder: /

But maybe it needs to be inseted in a different location.

Also, it has been requested now for many versions to add in stanza (without having to run manifest create)

./openshift-install create manifests
vi /home/core/ocpdev/openshift/99_openshift-cluster-api_worker-machineset-0.yaml
datacenter: acme_datacenter
datastore: vmfs00
folder: /datacenter/vm/demos/redhat/ocpdev
# Broken #resourcePool: /Production_Cluster/host/Production/Resources/NormalPriorityVMs
resourcePool: NormalPriorityVMs
server: vcenter01.acme.local

#

This means every cluster built gets dumped in wrong location and also that the policy of "least privilege access" for service account (Ex: ocpdeploy@vsphere.local) to deploy OCP runs into issue within vcenter as the customer cannot limit to sub folder and limited resource pool.