Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#805 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
node.js, typescript
Área
cli, developer-experience

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
53
Forks
28
Merge medio
4 d 12 h
PR fusionados (30 d)
61

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de elastic/cli

Todos los issues de elastic/cli

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.