[docs] Add aspire destroy command reference documentation#857
Merged
davidfowl merged 3 commits intoMay 6, 2026
Merged
Conversation
Documents the aspire destroy command including the new requirement that --yes must be passed when using --non-interactive. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
7bae38e to
065525f
Compare
eerhardt
reviewed
May 6, 2026
eerhardt
reviewed
May 6, 2026
eerhardt
reviewed
May 6, 2026
eerhardt
approved these changes
May 6, 2026
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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#16806
@aspire-repo-bot[bot]Target branch
Falling back to
mainbecauserelease/13.3does not exist onmicrosoft/aspire.dev.Why this PR is needed
microsoft/aspire#16806 introduced a breaking behavioral change to the
aspire destroyCLI command: when--non-interactiveis specified,--yesis now also required. Previously, scripts and automation could runaspire destroy --non-interactivewithout confirmation; now that produces an error:The
aspire destroycommand had no existing documentation on aspire.dev, so this PR creates the command reference page and adds it to the sidebar navigation.Summary of changes
src/frontend/src/content/docs/reference/cli/commands/aspire-destroy.mdx— new command reference page documenting all options, including a note on non-interactive usage requiring--yessrc/frontend/config/sidebar/reference.topics.ts— addedaspire destroyto the CLI sidebar afteraspire deployFiles modified
src/frontend/src/content/docs/reference/cli/commands/aspire-destroy.mdxsrc/frontend/config/sidebar/reference.topics.ts