solrConnectionString and templateLinkAccessToken from null to "" #27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We use the combination of Azure DevOps, Sitecore Quickstart ARM Templates and custom powershell scripts to automate the Sitecore PaaS provisioning.
I've been trying to use use Sitecore-Azure-Quickstart-Templates to install SXA on a (vanilla) Sitecore 9.0.2 XP env in Azure. The solution is fully PaaS using Azure search. But I kept running into the error:
If I pass an empty string for the templateLinkAccessToken variable, I then get this error:
I asked the the question on Sitecore Slack and had a few responses but didn't have much joy.
I've referenced other templates (Sitecore Commerce 9.0.2 and XP 9.0.2) and found the values for solrConnectionString and templateLinkAccessToken were set to "" and not null. I tried for a couple of days to pass a null/empty value into these variables via Azure DevOps and kept running into some form of the above mentioned errors.
So to make the SXA template consistent with the Commerce and XP 9.0.2 templates, I finally decided to fork the template and change the values in the template itself from null to "" and was able to successfully initialize a ARM deployment in first go (only passing in the parameters as per the Readme.)
This is why I'm submitting this Pull request for your review and a possible merge into the master branch so It's available to every other user.