|
1 | 1 | [!INCLUDE [Sandbox explanation](../../includes/azure-template-exercise-sandbox-subscription.md)]
|
2 | 2 |
|
3 |
| -You're starting to work on your R&D team's requests, and you decide to start by building an Azure Cosmos DB database for the toy drone's test data. In this exercise, you create the Azure Cosmos DB account and two child resources, one by using the `parent` property and the other as a nested resource. |
| 3 | +You're starting to work on your R&D team's requests. You decide to start by creating an Azure Cosmos DB database for the toy drone's test data. In this exercise, you create the Azure Cosmos DB account and two child resources. You create one child resource by using the `parent` property and the other as a nested resource. |
4 | 4 |
|
5 | 5 | During the process, you:
|
6 | 6 |
|
7 | 7 | > [!div class="checklist"]
|
8 |
| -> * Create a Bicep file that deploys a Cosmos DB account. |
9 |
| -> * Add a database and container, which are child resources of the Cosmos DB account. |
| 8 | +> * Create a Bicep file that deploys an Azure Cosmos DB account. |
| 9 | +> * Add a database and container, both of which are child resources of the Azure Cosmos DB account. |
10 | 10 | > * Deploy the template and verify the deployment.
|
11 | 11 |
|
12 | 12 | [!INCLUDE [Install the Bicep extension for Visual Studio Code](../../includes/azure-template-bicep-exercise-vscode-extension.md)]
|
13 | 13 |
|
14 | 14 | ## Create a Bicep template that contains an Azure Cosmos DB account
|
15 | 15 |
|
16 |
| -First, you create a new Bicep template with an Azure Cosmos DB account. To do so: |
| 16 | +First, you create a new Bicep template that contains an Azure Cosmos DB account. To do so: |
17 | 17 |
|
18 | 18 | 1. Open Visual Studio Code.
|
19 | 19 |
|
20 | 20 | 1. Create a new file called *main.bicep*.
|
21 | 21 |
|
22 | 22 | 1. Save the empty file so that Visual Studio Code loads the Bicep tooling.
|
23 | 23 |
|
24 |
| - You can either select **File** > **Save As** or press <kbd>Ctrl+S</kbd> in Windows (<kbd>⌘+S</kbd> on macOS). Be sure to remember where you saved the file. For example, you might want to create a *scripts* folder to save it in. |
| 24 | + You can either select **File** > **Save As** or select <kbd>Ctrl+S</kbd> in Windows (<kbd>⌘+S</kbd> on macOS). Be sure to remember where you saved the file. For example, you might want to create a *scripts* folder to save it in. |
25 | 25 |
|
26 | 26 | 1. Add the following content to the file. It's a good idea to enter it manually rather than copy and paste it. That way, you can see how the tooling helps you write your Bicep files.
|
27 | 27 |
|
|
0 commit comments