microsoft / microsoft/aspire

[AspireE2E] `aspire destroy`: with unknown flags, it will execute successfully without any CLI error.

Open Beginner friendly
#16,327 1 comment 0 reactions 0 assignees View on GitHub
area-cli
Dominant language
C#
Stars
6.3k
Forks
991
Avg merge
2d 12h
Merged PRs (30d)
201

Description

**REGRESSION INFO:** New feature on Aspire 13.3

**INSTALL STEPS**
1. Clean machine: Windows11 25h2 x64
2. Install 10.0.202 SDK
3. Install Aspire CLI 13.3 : `iex "& { $(irm https://aspire.dev/install.ps1) } -Quality dev"`

**REPRO STEPS**
1. Open CMD, create an Aspire ASP.NET Core/Blazor Starter App using following commands:

`aspire new aspire-starter -n Aspire1`

1. Run unknown flags `aspire destroy --force`

**ACTUAL**
`aspire destroy --force` will execute successfully.
Image

**EXPECTED**
error: Unknown option '--force' Run 'aspire destroy --help' for more information.

**aspire destroy -h** info:

Image

Contributor guide

Open the contributing guide

Research direction

Start at the `aspire destroy` CLI entry point and reproduce the reported command with `aspire destroy --force` after creating the starter app. Verify that an unknown option produces the expected error and that normal `aspire destroy` behavior remains unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
cli
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.