Skip to content

Commit 1a6a0ed

Browse files
committed
Stub out ARM quickstart
1 parent fbfe3b3 commit 1a6a0ed

File tree

2 files changed

+136
-0
lines changed

2 files changed

+136
-0
lines changed
Lines changed: 133 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,133 @@
1+
---
2+
title: Create a Service Fabric cluster by using Azure Resource Manager template
3+
description: Learn how to create an Azure Service Fabric cluster by using Azure Resource Manager template.
4+
author: erikadoyle
5+
ms.service: service-fabric
6+
ms.topic: quickstart
7+
ms.custom: subject-armqs
8+
ms.author: edoyle
9+
ms.date: 04/22/20
10+
---
11+
# The H1 heading must include words "Resource Manager template"
12+
13+
<!-- The second paragraph must be the following include file. You might need to change the file path of the include file depending on your content structure. This include is a paragraph that consistently introduces ARM concepts before doing a deployment and includes all our desired links to ARM content.-->
14+
15+
16+
[!INCLUDE [About Azure Resource Manager](../../includes/resource-manager-quickstart-introduction.md)]
17+
18+
If you don't have an Azure subscription, create a [free](https://azure.microsoft.com/free/) account before you begin.
19+
20+
## Prerequisites
21+
22+
<!-- If there aren't any prerequisites, just place "None" in the section. -->
23+
24+
## Create a ...
25+
26+
<!-- The second H2 must start with "Create a". For example, 'Create a Key Vault', 'Create a virtual machine', etc. -->
27+
28+
### Review the template
29+
30+
<!-- The first sentence must be the following sentence. The link is the quickstart template from GitHub. The link must begin with https://github.com/Azure/azure-quickstart-templates/. -->
31+
32+
The template used in this quickstart is from [Azure Quickstart templates]().
33+
34+
<!-- After the first sentence, add a JSON codefence that links to the quickstart template. Customers have provided feedback that they prefer to see the whole template; therefore, we recommend you include the whole template in your article. If your template is too long to show in the quickstart, you can instead add a sentence that says "The template for this article is too long to show here. To view the template, see ..."
35+
36+
The syntax for the codefence is: -->
37+
38+
:::code language="json" source="~/quickstart-templates/<TEMPLATE NAME>/azuredeploy.json" range="000-000" highlight="000-000":::
39+
40+
<!-- After the JSON codefence, a list of each resourceType from the JSON must exist with a link to the template reference starting with /azure/templates. For example:
41+
42+
* [**Microsoft.KeyVault/vaults**](/azure/templates/microsoft.keyvault/vaults): create an Azure key vault.
43+
* [**Microsoft.KeyVault/vaults/secrets**](/azure/templates/microsoft.keyvault/vaults/secrets): create an key vault secret.
44+
45+
The URL usually appears as, for example, https://docs.microsoft.com/en-us/azure/templates/Microsoft.Network/2019-11-01/loadBalancers for loadbalancer of Microsoft.Network. Remove the API version from the URL, the URL redirects the users to the latest version.
46+
-->
47+
48+
* [Azure resource type](link to the template reference)
49+
* [Azure resource type](link to the template reference)
50+
51+
<!-- List additional quickstart templates. For example: [Azure Quickstart Templates](https://azure.microsoft.com/resources/templates/?resourceType=Microsoft.Keyvault&pageNumber=1&sort=Popular).
52+
Notice the resourceType and sort elements in the URL.
53+
-->
54+
55+
## Deploy the template
56+
57+
<!--
58+
One of the following options must be included:
59+
60+
- **CLI**: In an Azure CLI Interactive codefence must contain **az group deployment create**. For example:
61+
62+
```azurecli-interactive
63+
read -p "Enter a project name that is used for generating resource names:" projectName &&
64+
read -p "Enter the location (i.e. centralus):" location &&
65+
templateUri="https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/101-storage-account-create/azuredeploy.json" &&
66+
resourceGroupName="${projectName}rg" &&
67+
az group create --name $resourceGroupName --location "$location" &&
68+
az group deployment create --resource-group $resourceGroupName --template-uri $templateUri
69+
echo "Press [ENTER] to continue ..." &&
70+
read
71+
```
72+
73+
- **PowerShell**: In an Azure PowerShell Interactive codefence must contain **New-AzResourceGroupDeployment**. For example:
74+
75+
```azurepowershell-interactive
76+
$projectName = Read-Host -Prompt "Enter a project name that is used for generating resource names"
77+
$location = Read-Host -Prompt "Enter the location (i.e. centralus)"
78+
$templateUri = "https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/101-storage-account-create/azuredeploy.json"
79+
80+
$resourceGroupName = "${projectName}rg"
81+
82+
New-AzResourceGroup -Name $resourceGroupName -Location "$location"
83+
New-AzResourceGroupDeployment -ResourceGroupName $resourceGroupName -TemplateUri $templateUri
84+
85+
Read-Host -Prompt "Press [ENTER] to continue ..."
86+
87+
For an example, see Add a description. Press tab when you are done.
88+
```
89+
90+
- **Portal**: A button with description **Deploy Resource Manager template to Azure**, with image **/media/<QUICKSTART FILE NAME>/deploy-to-azure.png*, must exist and have a link that starts with **https://portal.azure.com/#create/Microsoft.Template/uri/**:
91+
92+
```markdown
93+
[![Deploy to Azure](./media/quick-create-template/deploy-to-azure.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2F101-key-vault-create%2Fazuredeploy.json)
94+
```
95+
96+
To get the standard button image and find more information about this deployment option, see [Use a deployment button to deploy templates from GitHub repository](/azure/azure-resource-manager/templates/deploy-to-azure-button.md).
97+
-->
98+
99+
## Review deployed resources
100+
101+
<!-- You can also use the title "Validate the deployment"-->
102+
103+
## Clean up resources
104+
105+
When no longer needed, delete the resource group, which deletes the resources in the resource group.
106+
107+
<!--
108+
109+
Choose Azure CLI, Azure PowerShell, or Azure portal to delete the resource group. Use [Zone pivots](https://review.docs.microsoft.com/help/contribute/zone-pivots?branch=master) if you want to use multiple options. Here are the samples for Azure CLI and Azure PowerShell:
110+
111+
```azurecli-interactive
112+
echo "Enter the Resource Group name:" &&
113+
read resourceGroupName &&
114+
az group delete --name $resourceGroupName &&
115+
echo "Press [ENTER] to continue ..."
116+
```
117+
118+
```azurepowershell-interactive
119+
$resourceGroupName = Read-Host -Prompt "Enter the Resource Group name"
120+
Remove-AzResourceGroup -Name $resourceGroupName
121+
Write-Host "Press [ENTER] to continue..."
122+
```
123+
124+
-->
125+
126+
## Next steps
127+
128+
<!-- You can either make the next steps similar to the next steps in your other quickstarts, or point users to the following tutorial.-->
129+
130+
For a step-by-step tutorial that guides you through the process of creating a template, see:
131+
132+
> [!div class="nextstepaction"]
133+
> [ Tutorial: Create and deploy your first Azure Resource Manager template](/azure/azure-resource-manager/templates/template-tutorial-create-first-template.md)

articles/service-fabric/toc.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,9 @@
77
- name: Quickstarts
88
expanded: true
99
items:
10+
- name: ARM template
11+
displayName: Resource Manager
12+
href: quickstart-cluster-template.md
1013
- name: Create .NET application
1114
href: service-fabric-quickstart-dotnet.md
1215
- name: Deploy a Linux container application

0 commit comments

Comments
 (0)