You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This five-node Windows cluster is secured with a self-signed certificate and thus only intended for instructional purposes (rather than production workloads). We'll use and Azure CLI or Azure PowerShell to deploy the Bicep file.
18
+
This five-node Windows cluster is secured with a self-signed certificate and thus only intended for instructional purposes (rather than production workloads). We'll use Azure PowerShell to deploy the Bicep file.
19
19
20
20
## Prerequisites
21
21
@@ -25,12 +25,12 @@ If you don't have an Azure subscription, create a [free](https://azure.microsoft
25
25
26
26
To complete this quickstart, you'll need to install the [Service Fabric SDK and PowerShell module](service-fabric-get-started.md).
27
27
28
-
### Download the sample template and certificate helper script
28
+
### Download the sample Bicep file and certificate helper script
29
29
30
-
Clone or download the [Azure Resource Manager quickstart Templates](https://github.com/Azure/azure-quickstart-templates) repo. Alternatively, copy down locally the following files we'll be using from the *service-fabric-secure-cluster-5-node-1-nodetype* folder:
30
+
Clone or download the [Azure Resource Manager Quickstart Templates](https://github.com/Azure/azure-quickstart-templates) repo. Alternatively, copy down locally the following files we'll be using from the *service-fabric-secure-cluster-5-node-1-nodetype* folder:
@@ -68,7 +68,7 @@ The script will prompt you for the following (be sure to modify *CertDNSName* an
68
68
***KeyVaultName:***SFQuickstartKV*
69
69
***KeyVaultSecretName:** clustercert
70
70
71
-
Upon completion, the script will provide the parameter values needed for template deployment. Be sure to store these in the following variables, as they will be needed to deploy your cluster template:
71
+
Upon completion, the script will provide the parameter values needed for deployment. Be sure to store these in the following variables, as they will be needed for deployment:
72
72
73
73
```powershell
74
74
$sourceVaultId = "<Source Vault Resource Id>"
@@ -131,7 +131,7 @@ For example:
131
131
132
132
## Deploy the Bicep file
133
133
134
-
Store the paths of your ARM template and parameter files in variables, then deploy the template.
134
+
Store the paths of your Bicep file and parameter file in variables, then deploy the Bicep file.
135
135
136
136
```powershell
137
137
$templateFilePath = "<full path to azuredeploy.json>"
0 commit comments