Skip to content

Commit cdb958c

Browse files
updates
1 parent eaee3a3 commit cdb958c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/static-web-apps/publish-bicep.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ You can use a Bicep file to create an instance of Azure Static Web Apps. Bicep p
1616

1717
The steps in this article show you how to use Bicep to create a resource group and a Static Web Apps instance. After your static web app is created you still need to deploy your code using the typical methods of GitHub Actions, or using Azure Pipelines.
1818

19-
## Tools for resource creation
19+
## Resource creation tool
2020

2121
Bicep is one of several tools you can use to create resources in Azure. These tools include:
2222

@@ -100,7 +100,7 @@ The code in the previous section demonstrates how to create a static web app usi
100100

101101
To link your Functions app to your static web app, you need the `resourceId` of your Functions App. You can get this value from the Azure portal, or you can use the following command to return your Functions app `resourceId`.
102102

103-
```bash
103+
```azurecli
104104
az functionapp show -n <FUNCTION-APP-NAME> -g <RESOURCE-GROUP-NAME> --query id --output tsv
105105
```
106106

0 commit comments

Comments
 (0)