aspire config command
此内容尚不支持你的语言。
aspire config - Manage configuration settings.
Synopsis
Section titled “Synopsis”aspire config [command] [options]Description
Section titled “Description”The aspire config command manages the Aspire CLI config settings.
Starting in Aspire 13.2, Aspire prefers a rooted aspire.config.json file for
project-scoped configuration. The CLI can also read and write user-scoped global
defaults.
-
Project-scoped configuration
Project-scoped settings live in a rooted
aspire.config.jsonfile. This replaces the older.aspire/settings.jsonmodel. -
Global configuration
User-scoped defaults can be set with
aspire config set --global .... Project-scoped settings override global values when both are present. Project-specific values such asappHost.pathmust be configured locally inaspire.config.json.
Options
Section titled “Options”The following options are available:
-
-?, -h, --helpPrints help and usage documentation for the available commands and options.
-
-l, --log-level <Critical|Debug|Error|Information|None|Trace|Warning>Set the minimum log level for console output. Use this option to increase diagnostics while troubleshooting or reduce output in scripted runs.
-
--non-interactiveRun the command in non-interactive mode, disabling all interactive prompts and spinners.
-
--nologoSuppress the startup banner and telemetry notice.
-
--bannerDisplay the animated Aspire CLI welcome banner.
-
--wait-for-debuggerWait for a debugger to attach before running a command.
Commands
Section titled “Commands”The following commands are available:
| Command | Status | Function |
|---|---|---|
aspire config list | Stable | List current configuration values, or all available feature flags with --all. |
aspire config get <key> | Stable | Get a configuration value. |
aspire config set <key> <value> | Stable | Set a configuration value. |
aspire config delete <key> | Stable | Delete a configuration value. |
Settings
Section titled “Settings”The following config settings are available:
| Logical key | Stored in aspire.config.json as | Description |
|---|---|---|
appHost.path | appHost.path | Project-scoped path to the default AppHost entry point. This setting must be configured in the local aspire.config.json file. |
channel | channel | Default Aspire channel used by channel-aware commands such as aspire new, aspire init, and aspire update. |
features.defaultWatchEnabled | features.defaultWatchEnabled | Enable or disable watch mode by default when running Aspire applications for automatic restarts on file changes. |
features.experimentalPolyglot:go | features.experimentalPolyglot:go | Enable or disable experimental Go AppHost support. |
features.experimentalPolyglot:java | features.experimentalPolyglot:java | Enable or disable experimental Java AppHost support. |
features.experimentalPolyglot:python | features.experimentalPolyglot:python | Enable or disable experimental Python AppHost support. |
features.experimentalPolyglot:rust | features.experimentalPolyglot:rust | Enable or disable experimental Rust AppHost support. |
features.polyglotIntegrationFilterEnabled | features.polyglotIntegrationFilterEnabled | Enable or disable filtering aspire add, aspire integration list, and aspire integration search results to only integrations compatible with a non-C# AppHost. Disabled by default because remote NuGet feeds don’t reliably answer the tags:polyglot query used to build the compatibility allow-list. |
features.showAllTemplates | features.showAllTemplates | Show all available templates, including experimental ones, in aspire new and aspire init. |
features.showDeprecatedPackages | features.showDeprecatedPackages | Show or hide deprecated packages in aspire add search results. |
features.updateNotificationsEnabled | features.updateNotificationsEnabled | Enable or disable Aspire CLI update notifications. |
overrideStagingFeed | overrideStagingFeed | Escape hatch that always allows the staging channel to be resolved, regardless of the running CLI’s build identity. Set this to the staging feed URL you want channel-aware commands (aspire new, aspire init, aspire update) to use, for example: aspire config set -g overrideStagingFeed <feed-url>. Without this setting, --channel staging only resolves on stable or staging Aspire CLI builds — daily, local, and per-PR builds refuse it and report the recovery options. |