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

Deployer appends known hosts rather than replacing them

Abierto
#62 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
48/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
github-actions
Área
devops, documentation

Línea de trabajo

Locate the documentation for the known hosts option and read how its current behavior is described. Update that documentation to state whether entries are appended or replaced, then verify the wording clearly explains the resulting SSH fingerprint behavior.

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

Descripción

TLDR: the known hosts option implies it replaces the file, but it actually appends to it, which is not mentioned!

We've added the new github RSA fingerprints to a known hosts secret, along with several others, then told deployer to use it.

Unfortunately, deployer appends these to a known hosts file that has out of date fingerprints rather than replacing/overwriting, so we still get the SSH fingerprint problem despite adding the new entries.

As a workaround we're going to test removing all github fingerprints before running the deployer, but the documentation should be updated to make it clear that the action appends/extends, and does not replace/overwrite as currently implied

Upvote & Fund

  • We're using Polar.sh so you can upvote and help fund this issue.
  • We receive the funding once the issue is completed & confirmed by you.
  • Thank you in advance for helping prioritize & fund our backlog.
Fund with Polar
Lenguaje dominante
TypeScript
Estrellas
269
Forks
56
Sin PR fusionados en 30 d

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

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 deployphp/action

Todos los issues de deployphp/action

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.