[Suggestion]: VCF Version using Dual Site Deployment - Documentation Upgrade

Holorouter Version

9.1

VCF Version

VCF 9.1

Target Type

vCenter Cluster

Describe the bug

I have a suggestion about dual site deployment. I was trying to use Site A with VVF 9.0.2 and when I try to deploy Site B as a VCF 9.1.0.0 (using -Version "9.1.0.0" as an argument of "New-HolodeckInstance" command, the VCF deployed result is an 9.0.2.0.

I cannot find this information on documentation and after some hours I figure out that we need a New-HolodeckConfig to use the "side b" json, even though the command to create a new configuration now automatically creates separate JSON files for site A and site B.

Reproduction steps

1. Create a New Config
2. Deploy something on version 9.0.2.0, for example
3. Import "side b" of the same previosly config
4. Try to deploy something other than 9.0.2.0
5. Create a second "New Config"
6. Import "side b" from this new config
7. Try to deploy something other than 9.0.2.0

Expected behavior

1. The first attempt is likely to fail.
2. The second attempt with the new file should work with a different version of site A.

Relevant logs

Additional context

No response