Skip to content

Troubleshooting doc updates #262

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Oct 17, 2024
Merged

Troubleshooting doc updates #262

Show file tree
Hide file tree
Changes from 6 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
ffae721
use variable for group name
KSchlobohm Oct 17, 2024
bf28795
Alternate error message text
KSchlobohm Oct 17, 2024
128588f
add troubleshooting tip
KSchlobohm Oct 17, 2024
f14d852
let AZD handle single group tear down
KSchlobohm Oct 17, 2024
a71274d
add exit statement
KSchlobohm Oct 17, 2024
4298efc
fix environment var name reference
KSchlobohm Oct 17, 2024
97e3b63
Update testscripts/cleanup.ps1
KSchlobohm Oct 17, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion infra/scripts/postprovision/call-create-app-registrations.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
1 change: 1 addition & 0 deletions prod-deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
7 changes: 7 additions & 0 deletions testscripts/cleanup.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
# exitig 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) {
Expand Down
5 changes: 5 additions & 0 deletions troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
Loading