[docs] Document that azure-environment is hidden when all resources use emulators - #1618
Draft
aspire-repo-bot[bot] wants to merge 1 commit into
Draft
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
aspire-repo-bot
Bot
added
the
docs-from-code
14 tasks
Contributor
Author
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents changes from microsoft/aspire#19843
@eerhardtTargeting
release/13.6based on the source PR milestone13.6.Why
AppHosts that run every Azure resource through a local emulator previously showed an
azure-environmentresource stuck in the Not started state on the dashboard. The linked PR hides that control resource when the completed run-mode model has no Azure resources requiring provisioning, keeping it visible for mixed emulator/cloud models. The PR body includes a### User-facing usagesection (the triggeredpr_body_has_user_facing_sectionsignal), so this is a user-facing dashboard behavior change that was not previously documented.What changed
integrations/cloud/azure/overview.mdx: added a note under Local emulators explaining that Aspire hides theazure-environmentresource from the dashboard when every Azure resource is configured withRunAsEmulator, and that it reappears once any resource requires provisioning.whats-new/aspire-13-6.mdx: added a bullet under Testing, interactions, and extension points (App model and AppHost section) summarizing the cleaner emulator-only dashboard behavior, with a cross-reference to the local emulators section.Both are edits to existing pages; no new pages were created.