You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After using Azure Developer CLI to deploy to Azure, when I view the Aspire Dashboard, I got this error
There was an unhandled exception on the current circuit, so this circuit will be terminated. For more details turn on detailed exceptions by setting 'DetailedErrors: true' in 'appSettings.Development.json' or set 'CircuitOptions.DetailedErrors'.
Initializing an app to run on Azure (azd init)
? How do you want to initialize your app? Use code in the current directory
SUCCESS: Your app is ready for the cloud!
You can provision and deploy your app to Azure by running the azd up command in this directory. For more information on configuring your app, see ./next-steps.md
PS C:\dotnet\sample\eShop\src\eShop.AppHost> azd up
? Select an Azure Subscription to use: 1. Visual Studio Professional Subscription
? Select an Azure location to use: 16. (Asia Pacific) Southeast Asia (southeastasia)
Packaging services (azd package)
Provisioning Azure resources (azd provision)
Provisioning Azure resources can take some time.
Subscription: Visual Studio Professional Subscription
Location: Southeast Asia
After using Azure Developer CLI to deploy to Azure, when I view the Aspire Dashboard, I got this error
There was an unhandled exception on the current circuit, so this circuit will be terminated. For more details turn on detailed exceptions by setting 'DetailedErrors: true' in 'appSettings.Development.json' or set 'CircuitOptions.DetailedErrors'.
Initializing an app to run on Azure (azd init)
? How do you want to initialize your app? Use code in the current directory
(✓) Done: Scanning app code in current directory
Detected services:
.NET (Aspire)
Detected in: C:\dotnet\sample\eShop\src\eShop.AppHost\eShop.AppHost.csproj
azd will generate the files necessary to host your app on Azure using Azure Container Apps.
? Select an option Confirm and continue initializing my app
? Enter a new environment name: [? for help] eshopdev
? Enter a new environment name: eshopdev
Generating files to run your app on Azure:
(✓) Done: Generating ./azure.yaml
(✓) Done: Generating ./next-steps.md
SUCCESS: Your app is ready for the cloud!
You can provision and deploy your app to Azure by running the azd up command in this directory. For more information on configuring your app, see ./next-steps.md
PS C:\dotnet\sample\eShop\src\eShop.AppHost> azd up
? Select an Azure Subscription to use: 1. Visual Studio Professional Subscription
? Select an Azure location to use: 16. (Asia Pacific) Southeast Asia (southeastasia)
Packaging services (azd package)
Provisioning Azure resources (azd provision)
Provisioning Azure resources can take some time.
Subscription: Visual Studio Professional Subscription
Location: Southeast Asia
You can view detailed progress in the Azure Portal:
https://portal.azure.com/#view/HubsExtension/DeploymentDetailsBlade/~/overview/id
(✓) Done: Resource group: rg-eshopdev
(✓) Done: Log Analytics workspace: law-mn6lmqyu7hkig
(✓) Done: Container Registry: acrmn6lmqyu7hkig
(✓) Done: Container Apps Environment: cae-mn6lmqyu7hkig
Deploying services (azd deploy)
(✓) Done: Deploying service basket-api
(✓) Done: Deploying service catalog-api
(✓) Done: Deploying service eventbus
(✓) Done: Deploying service identity-api
(✓) Done: Deploying service mobile-bff
(✓) Done: Deploying service order-processor
(✓) Done: Deploying service ordering-api
(✓) Done: Deploying service payment-processor
(✓) Done: Deploying service postgres
(✓) Done: Deploying service redis
(✓) Done: Deploying service webapp
(✓) Done: Deploying service webhooks-api
(✓) Done: Deploying service webhooksclient
Aspire Dashboard: https://aspire-dashboard.ext.proudcliff-xxx.southeastasia.azurecontainerapps.io
SUCCESS: Your up workflow to provision and deploy to Azure completed in 11 minutes 1 second.
PS C:\dotnet\sample\eShop\src\eShop.AppHost>
The text was updated successfully, but these errors were encountered: