OpenShift vSphere Connection Configuration Does Not Appropriately Insert Escaped Strings

Recently a user was attempting to change the Virtual Machine Folder for a cluster installed on vSphere.  The user used the configuration panel "vSphere Connection Configuration" to complete this process.  Upon updating the path and clicking "Save Configuration" cluster wide issues emerged including nodes not coming back online after a reboot. 

OpenShift nodes eventually crashed with an error resultant of an incorrectly parsed folder due to the string literal " " characters missing.

While this was exhibited on OCP 4.13, other versions may be affected.