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

Allow silencing the keyring-unavailable warning on headless machines

Abierto
  • ¿Algo no está bien?
#522 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
cli, security

Línea de trabajo

Start by locating the code that emits the “system keyring unavailable” warning, then trace how credential-store selection and the --json and --quiet paths handle warnings. Before changing behavior, resolve which requested option is intended; done should cover deliberate file-store selection, appropriate warning behavior for interactive and structured-output runs, and regression coverage.

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

Descripción

Context

On a headless Linux server with no Secret Service or keyring, every hey invocation prints:

warning: system keyring unavailable, credentials stored in plaintext at ~/.config/hey-cli/credentials.json

It prints on every call, including --json and --quiet runs. Scripts that capture stdout and stderr together, or that treat any stderr output as a problem, have to filter it out each time, and the line gets into logs and error messages. In our case the real error in a failure report was hidden behind this warning.

The plaintext file fallback is fine for this kind of machine, which runs as a dedicated user with 0600 permissions. The problem is only that the warning can't be turned off.

No account-specific details below.

Ask

  • A way to choose the file store deliberately and silence the warning: hey config set credential_store file, or an env var such as HEY_CREDENTIAL_STORE=file.
  • With --json, put the warning in the JSON (for example a warnings array) instead of writing it to stderr, or print it at most once per machine.
  • Keep showing it by default for interactive first-time setups, where it's useful.

Related (closed): #352, #453 (keyring behaviour on Linux).

Lenguaje dominante
Go
Estrellas
409
Forks
49
Merge medio
1 d 3 h
PR fusionados (30 d)
73

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 basecamp/hey-cli

Todos los issues de basecamp/hey-cli

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.