paul chipchase d0ded2296f Allow Mirage to connect to the perforce source control provider even if it was not specified in the config file or command line. ...

#rb PJ.Kack
#rnx
#preflight 60fff7d57f21c90001f9399d

- When we check the source control provider name, we will now attempt to set it to "Perforce" if it is current the default "None" provider.
- If the user has specified a different source control provider than "Perforce" we will give a fatal error that the content virtualization graph containing the source control backend will not work with that setup.
- This part of the workflow might need to change in the future or at least the Mirage documentation must make very clear that when using source control as the persistent storage backend that a connection to perforce will be required, at least until we support our source control solutions but even then the connect to that provider will be required.

[CL 16968160 by paul chipchase in ue5-main branch]

2021-07-27 09:45:11 -04:00

..

Private

Allow Mirage to connect to the perforce source control provider even if it was not specified in the config file or command line.

2021-07-27 09:45:11 -04:00

Virtualization.Build.cs

…