Troubleshooting doc updates (#262)

- add troubleshooting tip into prod doc
- add alternate troubleshooting error message text
- fix group name reported in log by script
- change to using AZD for single group tear down

---------

Co-authored-by: Mike Rousos <[email protected]>

Author: KSchlobohm

infra/scripts/postprovision/call-create-app-registrations.sh

@@ -11,6 +11,6 @@ fi
 # This script is run by azd pre-provision hook and is part of the deployment lifecycle run when deploying the code for the Relecloud web app.
 resourceGroupName=$((azd env get-values --output json) | jq -r .AZURE_RESOURCE_GROUP)
 
-echo "Calling create-app-registrations.ps1 for group:'resourceGroupName'..."
+echo "Calling create-app-registrations.ps1 for group:'$resourceGroupName'..."
 
 pwsh ./infra/scripts/postprovision/create-app-registrations.ps1 -ResourceGroupName $resourceGroupName -NoPrompt

prod-deployment.md

@@ -262,6 +262,7 @@ The following detailed deployment steps assume you are using a Dev Container ins
     ```pwsh
     azd deploy
     ```
+    > If you were unable to deploy due to [ERROR: getting target resource](troubleshooting.md#error-reauthentication-required-run-azd-auth-login---scope-httpsmanagementazurecomdefault-to-log-in)
 
     It takes approximately 5 minutes to deploy the code.
     

testscripts/cleanup.ps1

@@ -378,6 +378,13 @@ foreach ($resourceGroupName in $resourceGroups) {
     Remove-DiagnosticSettingsForResourceGroup -ResourceGroupName $resourceGroupName
 }
 
+if ($azdConfig['ENVIRONMENT'] ?? 'dev' -eq "dev") {
+    # when performing dev cleanup there are no dependencies between resource groups
+    # existing at this point allows AZD to handle the tear down responsibilities
+    "`nCleanup complete." | Write-Output
+    exit 0
+}
+
 # if $SkipResourceGroupDeletion is false, then we skip the resource group deletion
 # flag is expected to be set to false when combined with the `azd down` command
 if (-not $SkipResourceGroupDeletion) {

troubleshooting.md

@@ -106,9 +106,14 @@ This error can happen when you are using an account that has access to multiple
 
 Depending on your workflow you may get a different error message for the same issue:
 
+Option 1:
 ```sh
 ERROR: resolving bicep parameters file: fetching current principal id: getting tenant id for subscription...
 ```
+Option 2:
+```sh
+ERROR: getting target resource: getting service resource: resolving user access to subscription 'XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX' : reauthentication required, run `azd auth login --scope https://management.azure.com//.default` to log in
+```
 
 ### Workaround
 You should complete the MFA experience for your default tenant, and the tenant that you wish to access by running both authentication commands: