Lab 31 Observations

[pstueck]

Module: Create resource template for Azure Cosmos DB for NoSQL

all Bicep related course pages

Seems worth mentioning that Account, Database, Container after resource is just a name, not a command or directive.

Lab/Demo: 31

Task: all tasks with code snippets

Consider adding the Type icon (the green T) to the values in the table as well.
Sometimes typing something yourself makes remembering easier (but having an easy way to get to those class names, date values, … would be great).

Task: Create Azure Cosmos DB for NoSQL resources using Azure Resource Manager templates

Step: 22

Consider using a throughput RU/s value other than the default of 400 (e.g. 450, 500, …).

Task: Create Azure Cosmos DB for NoSQL resources using Bicep templates

Step: 3 & 7

The code snippet in step 3 is not az-cli linter friendly.
Running az-cli issues a warning no-loc-expr-outside-params about using resourceGroup().location instead of a parameter.

Step: 14

Consider using a throughput RU/s value other than the default of 400 (e.g. 450, 500, …). See also Step 22 when using ARM templates

[MScalopez]

Reviewing suggestions

[MScalopez]

notes: Step 22 - We will consider that change for a future version of the lab. While I believe you are suggesting that would help the learners understand we can change the default RU value, for the purpose of this lab it might not bring the desired effect since all we are trying to teach is how use ARM templates and Bicep files.

Steps 3 & 7, good catch, added parameter to bicep script to prevent warning message.

Step 14 - Please review my previous comment.

[pstueck]

I must admit, that “Step 22” and “Step 14” was more of a general idea through out the labs (and lab 31 was just the – pardon – “lucky loser” ;-) ). It just helps to discern various databases, containers and what not, when them all have their own RU/s.