In this blog I want to explain the path I have taken, (agreed the latest and greatest in terms of SiteCore version) should not be used for Production purposes for all good reasons. However trying the latest in releases gives the kicks of being on on the Edge.
So I will be using SAT 2.7 and Sitecore 10.2.0 for this discussion.
Referring to topologies, as we all know Sitecore supports a range of Topologies from XP0, XM, XMSingle, read here for more.
Certificates are very important entities, a great care to be taken while creating/generating them. The major lessons learnt during this process of deploying an Sitecore 10.2 XM0 is amazing.
Lessons learnt (common mistakes)
- Syntax: there has to be ” double quotes before and after when we define/set a attribute in JSON, commas “,” wherever necessary
$CertificateFile = ASDFE$T$%EADACDRERCC.pfx
$CertificateFile = “ASDFESDF#$#EACDED_)#(.pfx” - Having few files in the local where you are executing the powershell command and the rest in Azure Blob Storage is not advised. Use the Azure Storage Account Container for your files and get the SAS token/URL and use them for the Parameters
- DeploymentID names should be unique
- DeploymentID in the Parameter for Start-SitecoreAzureDeployment -Name
is different from the "params":{ "deploymentId":{"value":"someid"}, - RAW version
There are few important steps one have to follow to make this a breeze. Sitecore has provided a complete Walkthrough and the prerequisites so I was in the thick of it to completely understand and share my experience in the process.
However when you are trying the latest and greatest there are chances you can get to the end and still not complete. That is where I am at. Though I maintain to do the right thing as follows this is not working
- Different names for DeploymentId and “deploymentId”
- Have all the SCWDP uploaded to Azure Storage account and get the SAS URL (have these URLs to last longer)
- Have full permissions on the Azure Subscription
Leave a Reply