aws / aws/amazon-q-developer-cli
bug: "q integratioons status all" returns not-supported error
- Vorherrschende Sprache
- Rust
- Sterne
- 2k
- Forks
- 439
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
### Checks
- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again
### Operating system
MacOS
### Expected behaviour
Given that `q integrations status` says that it requires a subcommand, and that 'all' is included in that,
I expect `q integration status all` or `q integration status all -v` to be the equivalent of iterating over all the available integrations and returning their status
### Actual behaviour
`$ q integrations status all -v`
```
error:
0: Checking the status for all integrations is currently not supported
Location:
crates/q_cli/src/cli/integrations.rs:394
```
### Steps to reproduce
$ `q integrations status`
returns commands, including all
$ `q integrations status all`
error: Checking the status for all integrations is currently not supported
$ `q integrations status all -v`
```
error:
0: Checking the status for all integrations is currently not supported
Location:
crates/q_cli/src/cli/integrations.rs:394
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
```
### Environment
```yaml
```
Beitragsleitfaden
Rechercherichtung
Beginne bei crates/q_cli/src/cli/integrations.rs:394 und verfolge die Verarbeitung von `q integrations status all` und seiner Option `-v`. Reproduziere den aktuellen Fehler mit den Befehlen aus dem Issue und überprüfe anschließend, dass der Befehl den Status aller verfügbaren Integrationen meldet, anstatt den Fehler „not supported“ zurückzugeben.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- rust
- Bereich
- cli
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 45/100