Fetch default_ config from Solr and use that for new config uploads

[DiLascio]

For easier maintainability of Sitecore version support, download the default_ config from an existing Solr deployment, modify that and re-upload it when creating new configs with connector

[DiLascio]

This requirement is currently unclear internally and needs to be put on hold.

[Vapok]

From Karan:

Yes, I gave him this requirement.

This requirement came up because currently whenever a new version of Sitecore comes out, we have to go in and manually create a new version of the config that is compatible with Solr/Sitecore combo and then upload it to the repo.

This change that we have to make to config, is always exactly the same.

• Create a new field called _uniqueid
• Change the Unique ID from id to _uniqueid
• Disable automatic field creation

That's it.

So my argument was, why do we need to add an unnecessary hurdle of updating the repo for a specific version of Sitecore where instead, we can just ask the script to download the config from Solr, make these edits, and then use this config.
This way we won't have to update the script for every new Sitecore version release.

1. Download the default config
2. Make a copy of it and update it to work with XP/XM
3. Upload the default config back and use it for XConnect
4. Upload the updated version and use it for XP/XM

This way we can support a new version of Sitecore the day it is released.