Merge branch 'main' into peckjon-patch-7

Author: peckjon

README.md

@@ -4,7 +4,7 @@ This repository contains the project for both a guided workshop and the Modern D
 
 ## Getting started
 
-> **[Get started learning about development and DevOps with GitHub!](pets-workshop/blob/main/content/README.md)**
+> **[Get started learning about development and DevOps with GitHub!](./content/README.md)**
 
 ## License 
 

content/guided-workshop/exercises/3-codespaces.md

@@ -20,7 +20,7 @@ One thing that's really great is the [default dev container](https://github.com/
 
 Let's create our own dev container! The [dev container is configured](https://docs.github.com/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers) by creating the Docker files Codespaces will use to create and configure the container, and providing any customizations in the `devcontainer.json` file. Customizations provided in `devcontainer.json` can include ports to open, commands to run, and extension to install in Visual Studio Code (either running locally on the desktop or in the browser). This configuration becomes part of the repository. All developers who wish to contribute can then create a new instance of the container based on the configuration you provided.
 
-1. Access the Command Palette (<kbd>F1</kbd>), then start typing **dev container**.
+1. Access the Command Palette (<kbd>F1</kbd> or clicking ☰ → View → Command Palette), then start typing **dev container**.
 1. Select **Codespaces: Add Development Container Configuration Files...** .
 1. Select **Create a new configuration...**.
 1. Select **From a predefined container configuration...**.
@@ -56,7 +56,7 @@ You've now defined a custom container!
 
 Whenever someone uses the codespace you defined they'll have an environment with Node.js and Mongo DB, and the GitHub Copilot extension installed. Let's use this container!
 
-1. Select <kbd>F1</kbd> to open the command palette.
+1. Open the command palette.
 1. Type **rebuild** and select **Codespaces: Rebuild container**.
 1. Select **Rebuild Container** on the dialog box. Your container now rebuilds.
 
@@ -68,7 +68,7 @@ Custom containers for GitHub Codespaces become part of the source code for the r
 
 > **IMPORTANT:** For purposes of this exercise we are pushing code updates directly to `main`, our default branch. Normally you would follow the [GitHub flow](https://docs.github.com/en/get-started/quickstart/github-flow), which we will do in a [later exercise](6-github-flow.md).
 
-1. Open the terminal window in the codespace by selecting <kbd>Ctl</kbd> + <kbd>`</kbd>.
+1. Open the terminal window in the codespace by selecting <kbd>Ctl</kbd> + <kbd>`</kbd> or clicking ☰ → View → Terminal.
 1. Find the issue number for defining the codespace by entering the following command:
 
     ```bash
@@ -81,7 +81,7 @@ Custom containers for GitHub Codespaces become part of the source code for the r
 
     ```bash
     git add .
-    git commit -m "Resolves <ISSUE_NUMBER>"
+    git commit -m "Resolves #<ISSUE_NUMBER>"
     git push
     ```
 
@@ -107,7 +107,7 @@ Let's add an environment variable, refresh the codespace to update the environme
 1. Select the **Settings** tab.
 1. On the left, under the **Security** section, expand **Secrets and variables** and select **Codespaces**.
 
-    ![Screenshot of the Secrets and variables section](https://docs.github.com/en/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)
+    ![Screenshot of the Secrets and variables section](./images/3-secrets-variables.png)
 
 1. Select **New repository secret**.
 1. Create a new secret by entering the following values and pressing **Add secret**.
@@ -132,6 +132,8 @@ Let's add an environment variable, refresh the codespace to update the environme
 
 1. You will now see a new tab with your website running! Notice the URL at the top, which resembles the name of your codespace. Your website is running in the container you defined in the cloud!
 
+    > **NOTE:** If you close this tab, you can reopen it by clicking the "Ports" tab next to the Terminal, mousing over the "Forwarded Address" starting with `https://`, then clicking the globe icon 
+
 1. If you wish, you can add a pet to the database by selecting **Add pet**. On the form you will notice various fields to describe the pet. If you need a URL for images, you can use any of the following:
 
     - https://raw.githubusercontent.com/github/pets-workshop/main/src/pics/roscoe.jpg

content/guided-workshop/exercises/5-coding.md

@@ -149,7 +149,7 @@ Let's see how GitHub Copilot can help us quickly create the component. We're goi
 1. Finally, ask GitHub Copilot to display today's hours:
 
     ```javascript
-    // display today and the hours in an div with an id of hours
+    // display a header of "Today's Hours", and the name of today and hours (in a paragraph), inside an div with an id of "hours"
     ```
 
 1. GitHub Copilot will likely suggest the following code line-by-line, which you can accept by pressing <kbd>Tab</kbd>:

content/guided-workshop/exercises/7-create-environment.md

@@ -210,6 +210,69 @@ You've prepped everything on both Azure and your repository, and created the wor
 
     The workflow will now run and create the resources! This will take several minutes. You may need to refresh the page to see it start running. Once running, you can navigate into the workflow run to view the log and track the progress.
 
+## Debugging the workflow
+
+If you see error messages such as:
+
+```
+Code: MissingSubscriptionRegistration
+Message: The subscription is not registered to use namespace {resource-provider-namespace}
+```
+
+For example:
+
+```
+Error: ERROR: ***"status":"Failed",
+"error":***"code":"DeploymentFailed",
+```
+
+```
+"target":"/subscriptions/***/resourceGroups/pets-workshop/providers/Microsoft.Resources/deployments/main",
+"message":"At least one resource deployment operation failed.
+Please list deployment operations for details.
+Please see https://aka.ms/arm-deployment-operations for usage details.",
+```
+
+```
+"details":[***"code":"MissingSubscriptionRegistration",
+"target":"Microsoft.App",
+"message":"The subscription is not registered to use namespace 'Microsoft.App'.
+See https://aka.ms/rps-not-found for how to register subscriptions."***]
+```
+
+```
+"details":[***"code":"MissingSubscriptionRegistration",
+"target":"Microsoft.ContainerRegistry",
+"message":"The subscription is not registered to use namespace 'Microsoft.ContainerRegistry'.
+See https://aka.ms/rps-not-found for how to register subscriptions."***]
+```
+
+```
+"details":[***"code":"MissingSubscriptionRegistration",
+"target":"Microsoft.DocumentDB",
+"message":"The subscription is not registered to use namespace 'Microsoft.DocumentDB'.
+See https://aka.ms/rps-not-found for how to register subscriptions."***]
+```
+
+```
+"details":[***"code":"MissingSubscriptionRegistration",
+"target":"Microsoft.OperationalInsights",
+"message":"The subscription is not registered to use namespace 'Microsoft.OperationalInsights'.
+See https://aka.ms/rps-not-found for how to register subscriptions."***]
+```
+
+You need to register resources via the Azure Portal first.
+
+Specifically, you need to register:
+* Microsoft.App
+* Microsoft.ContainerRegistry
+* Microsoft.DocumentDB
+* Microsoft.OperationalInsights
+
+Follow the instructions at
+
+https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/error-register-resource-provider?tabs=azure-portal#solution
+
 ## Summary and next steps
 
 Congratulations! You have new defined a workflow which uses infrastructure as code (IaC) to create the resources necessary for deployment. This allows you to quickly create a consistent environment, reducing overhead and errors. Let's close everything out by [implementing continuous deployment](8-deployment.md).