Skip to content

Commit 804b951

Browse files
committed
Edits to Bicep quickstart
1 parent d804a34 commit 804b951

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/service-fabric/quickstart-cluster-bicep.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Create a Service Fabric cluster using Bicep
33
description: In this quickstart, you will create an Azure Service Fabric test cluster using Bicep.
44
author: schaffererin
55
ms.author: v-eschaffer
6-
ms.date: 05/22/2022
6+
ms.date: 06/22/2022
77
ms.topic: quickstart
88
ms.service: service-fabric
99
ms.custom: devx-track-azurepowershell, subject-armqs, mode-arm
@@ -15,7 +15,7 @@ Azure Service Fabric is a distributed systems platform that makes it easy to pac
1515

1616
[!INCLUDE [About Bicep](../../includes/resource-manager-quickstart-bicep-introduction.md)]
1717

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 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.
1919

2020
## Prerequisites
2121

@@ -25,12 +25,12 @@ If you don't have an Azure subscription, create a [free](https://azure.microsoft
2525

2626
To complete this quickstart, you'll need to install the [Service Fabric SDK and PowerShell module](service-fabric-get-started.md).
2727

28-
### Download the sample template and certificate helper script
28+
### Download the sample Bicep file and certificate helper script
2929

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:
3131

3232
* [New-ServiceFabricClusterCertificate.ps1](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/quickstarts/microsoft.servicefabric/service-fabric-secure-cluster-5-node-1-nodetype/scripts/New-ServiceFabricClusterCertificate.ps1)
33-
* [azuredeploy.json](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/quickstarts/microsoft.servicefabric/service-fabric-secure-cluster-5-node-1-nodetype/azuredeploy.json)
33+
* [main.bicep](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/quickstarts/microsoft.servicefabric/service-fabric-secure-cluster-5-node-1-nodetype/main.bicep)
3434
* [azuredeploy.parameters.json](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/quickstarts/microsoft.servicefabric/service-fabric-secure-cluster-5-node-1-nodetype/azuredeploy.parameters.json)
3535

3636
### Sign in to Azure
@@ -68,7 +68,7 @@ The script will prompt you for the following (be sure to modify *CertDNSName* an
6868
* **KeyVaultName:** *SFQuickstartKV*
6969
* **KeyVaultSecretName:** clustercert
7070

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:
7272

7373
```powershell
7474
$sourceVaultId = "<Source Vault Resource Id>"
@@ -131,7 +131,7 @@ For example:
131131

132132
## Deploy the Bicep file
133133

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.
135135

136136
```powershell
137137
$templateFilePath = "<full path to azuredeploy.json>"

0 commit comments

Comments
 (0)