Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Feature Request] Show active context and target deployment in interactive command output

Aperta
  • Qualcosa non va?
#805 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
node.js, typescript
Ambito
cli, developer-experience

Direzione di ricerca

Start by locating the interactive command output and context selection paths, especially where --use-context is applied and where --json output is written. Check the existing CLI configuration and tests for output flags. Done means the selected context and target can be shown optionally while stdout, JSON, exit codes, and non-interactive behavior remain compatible; the issue does not identify specific files or tests.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Problem

When managing multiple Elasticsearch and Kibana deployments using Elastic CLI, it is not immediately obvious which deployment a command is targeting.

In our environment, engineers manage multiple customer deployments across several Elastic Cloud Enterprise (ECE) installations and self-managed Elastic Stack clusters.

Each deployment can have multiple contexts with different privilege levels, such as read-only and write-capable API keys.

This makes context awareness particularly important for operational safety.

Currently, the user must explicitly check the active context using elastic config current-context get or elastic status.

Proposed solution

Provide an optional context header for interactive command execution.

For example:

Elastic CLI
Context:    ece-eu01-customer-a-pr-01-ro
Target:     customer-a-pr-01
Endpoint:   https://es.example.com:9243
Access:     ro

[
  {
    "id": "dashboard-123",
    "title": "Infrastructure Overview"
  }
]

The header should show:

  • Effective context name.
  • Target Elasticsearch, Kibana or Cloud endpoint.
  • Optional human-readable deployment name or alias.
  • Configured permission profile, if explicitly available.

The context should reflect the context actually selected for the command, including --use-context, rather than simply displaying the default context.

Output compatibility

Preserving machine-readable output is essential.

Suggested behavior:

  • Disabled by default in non-interactive sessions.
  • Enabled optionally through a configuration setting or --show-context flag.
  • Display the header on stderr, leaving stdout unchanged.
  • Preserve valid JSON output when using --json or piping to jq.
  • Preserve existing exit codes and command behavior.
  • Support --no-context-header to suppress the header explicitly.

An alternative would be an interactive-only startup banner controlled by the existing CLI configuration.

Example configuration

output:
  context_header: interactive

Possible values:

  • never
  • interactive
  • always

The configuration syntax is only illustrative.

Additional considerations

The CLI should not infer actual privileges solely from context names like ro and rw. These names are conventions, not authorization guarantees.

An optional display label could be useful for long context names.

The feature should not require additional API requests just to print the header.

Environment

  • Elastic CLI v0.7.0
  • Rocky Linux 9.8
  • Node.js 24
  • Multiple Elastic Stack 9.x deployments
  • ECE and self-managed clusters
  • Named contexts using separate RO/RW API keys

Motivation

This would improve usability and reduce the risk of executing commands against an unintended customer or environment, without requiring shell wrappers or custom Bash prompt modifications.

Lingua principale
TypeScript
Stelle
53
Fork
28
Merge medio
23h 41m
PR unite (30g)
44

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di elastic/cli

Tutte le issue di elastic/cli

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.