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

Make the anonymous-operator audit gate config-driven: add `compliance.allow_anonymous_operator` beside `FORGELM_ALLOW_ANONYMOUS_OPERATOR`

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
security

Línea de trabajo

Start with the environment check in AuditLogger.__init__, then the same FORGELM_ALLOW_ANONYMOUS_OPERATOR reads in doctor and approve. Do not start until #706 is settled, since it may close this row instead. If the field is added, thread compliance.allow_anonymous_operator through those call sites with YAML taking precedence, and cover the precedence in a test. Done means the field is documented in EN and TR, the template is updated, and the row is removed from docs/roadmap/risks-and-decisions.md with its ID named in the CHANGELOG.

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

Descripción

area: config severity: low source: roadmap wave: 4

Deferred work · F-PR29-A6-14 · severity Low · cost ~30 min (more in practice) · recorded in docs/roadmap/risks-and-decisions.md:87

Summary

Whether the audit logger refuses to start when no operator identity resolves is decided only by the FORGELM_ALLOW_ANONYMOUS_OPERATOR=1 environment variable (read in AuditLogger.__init__, and again in doctor and approve). The config-driven principle keeps behaviour gates in validated YAML and environment variables for secrets. The PR #29 plan adds compliance.allow_anonymous_operator: bool = False, with YAML taking precedence and the variable kept as a CI fallback.

Condition or budget

None recorded. Settle #706 first: it proposes the opposite fix (documenting identity variables as permitted), which would make this row moot.

State today (re-checked 2026-10-09)

No allow_anonymous_operator field exists; AuditLogger takes no config, so the field has to be threaded through its call sites.

Related

#706 (CR-A13-063) — the competing fix; #714 (CR-A04-086) asks for one shared operator-identity helper.

Acceptance criteria

  • Either the field exists (description, template entry, EN/TR docs, precedence tested) or #706's position is adopted and this row is closed with that reason.
  • The row is removed from the deferral table and the CHANGELOG names its ID (the table's removal contract).

Recorded in docs/roadmap/risks-and-decisions.md (read at f94595f) and re-checked against the code on 2026-10-09. The row leaves that table only when the fix is on main, the CHANGELOG names its ID and any promised guard exists.

Lenguaje dominante
Python
Estrellas
9
Forks
1
Merge medio
8 h 10 min
PR fusionados (30 d)
5

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 HodeTech/ForgeLM

Todos los issues de HodeTech/ForgeLM

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.