Skip to content

Hide azure-environment when all Azure resources use emulators #19617

Description

Description

When every Azure resource in an AppHost is configured to run as a local emulator, the dashboard still shows an azure-environment resource in the Not started state.

This adds noise to the resource list and suggests that part of the application has not started, even though no Azure provisioning environment is needed for the local run.

Expected behavior

azure-environment should be hidden when all Azure resources in the model use emulators and no resource needs Azure provisioning. Alternatively, it could be hidden by default unless it participates in the current run.

Actual behavior

azure-environment appears as a visible, Not started resource alongside otherwise running emulator resources.

Reproduction

Using Aspire CLI/SDK 13.5.2 with a TypeScript AppHost, configure Azure resources exclusively with local emulators, for example:

  • Azure Cosmos DB with runAsPreviewEmulator
  • Azure Storage with runAsEmulator
  • Azure Event Hubs with runAsEmulator

Start the AppHost and open the Resources page in the dashboard. The azure-environment resource remains visible in the Not started state.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

area-app-modelIssues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplicationarea-integrationsIssues pertaining to Aspire Integrations packagestriage:bot-seenAspire triage bot has seen this issue

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions