[docs] Remove execCommandEnabled from CLI config settings reference#901
Merged
davidfowl merged 1 commit intoMay 11, 2026
Merged
Conversation
The aspire exec command was removed in microsoft/aspire#16913. Remove the associated execCommandEnabled feature flag entry from the CLI configuration settings reference table. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
aspire-repo-bot
Bot
added
the
docs-from-code
14 tasks
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
1 participant
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#16913 by
@davidfowl.Targeting
mainbecauserelease/13.4does not yet exist onmicrosoft/aspire.dev.Why this PR is needed
The
aspire execcommand was an experimental CLI command gated behind theexecCommandEnabledfeature flag. microsoft/aspire#16913 removed the command entirely (it was a breaking change). The CLI configuration settings reference table on the docs site still listedfeatures.execCommandEnabledas a valid setting, which would confuse users trying to use a feature that no longer exists.What was changed
Removed the
features.execCommandEnabledrow from the CLI config settings reference table.Files modified
src/frontend/src/content/docs/reference/cli/includes/config-settings-table.md— removed thefeatures.execCommandEnabledentry