[docs] aspire update: document --yes required with --non-interactive#902
Merged
davidfowl merged 2 commits intoMay 11, 2026
Conversation
The aspire update command now validates that --yes is provided when --non-interactive is specified, matching the existing behavior of aspire destroy. Add a Non-interactive usage section to the update command docs to make this requirement explicit. Documents changes from microsoft/aspire#16829 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
aspire-repo-bot
Bot
added
the
docs-from-code
JamesNK
approved these changes
May 11, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the aspire update CLI reference documentation to reflect the new validation behavior requiring --yes when running with --non-interactive, aligning docs with the CLI’s enforced behavior (mirroring aspire destroy).
Changes:
- Added a “Non-interactive usage” section explaining that
--yesmust be used with--non-interactive. - Documented the error message shown when
--non-interactiveis used without--yes.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
davidfowl
approved these changes
May 11, 2026
davidfowl
deleted the
docs/update-command-non-interactive-yes-required-93890821725613de
branch
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#16829 by
@JamesNK.Targeting
main(falling back tomainbecauserelease/13.4does not yet exist onmicrosoft/aspire.dev).Why this PR is needed
PR microsoft/aspire#16829 added validation to the
aspire updatecommand so that--yesis required when--non-interactiveis specified. This matches the existing behavior ofaspire destroy. Without this docs update, CLI users wouldn't know that omitting--yeswhile using--non-interactiveresults in an error.What was changed
Added a Non-interactive usage section to the
aspire updatecommand reference page, explaining:--yesmust be provided alongside--non-interactive--yesis omittedThis mirrors the existing documentation pattern used by
aspire destroy.Files modified
src/frontend/src/content/docs/reference/cli/commands/aspire-update.mdx— updated (added Non-interactive usage section)