Fail sample validation when Bicep warns that PostgreSQL TLS settings are unsupported

Abierto
#2,053 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
75/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions
Área
ci-cd, testing

Línea de trabajo

Start with .github/scripts/validate_bicep.py and the existing .github/workflows/validate-bicep.yaml; add focused standard-library unittest fixtures beside the validator and run them before compilation in the workflow. Cover the listed diagnostic, path, unrelated-warning, and normal-error cases. Done means the PostgreSQL TLS warnings fail validation even when Bicep exits zero, while unrelated warnings remain allowed and normal error handling and samples' strict validation are preserved.

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

Descripción

triaged

What content needs to be created or modified?

The Bicep validation job can pass while the compiler emits BCP036 Warning for an unsupported PostgreSQL tls value.

Describe the solution you'd like

In the existing validator, fail BCP036/BCP037 diagnostics directly naming tls in the PostgreSQL demo even when Bicep exits zero. Match the diagnostic's actual source path as well as the compiled sample path; do not promote warnings from unrelated imported files. Do not rely on fixed line numbers or fail every lint warning. Preserve normal error/nonzero handling.

Add standard-library unittest fixtures for clean output, exit-zero TLS warnings, both diagnostic codes, source attribution, relative/absolute paths, unrelated properties/codes/files, and normal errors. Run them before compilation in the existing workflow. Coordinate semantics with samples without weakening its separate strict validation.

Where should the new material be placed?

.github/scripts/validate_bicep.py, focused tests beside it, and .github/workflows/validate-bicep.yaml.

The associated pull request from the Radius code repo, if applicable

N/A. Split from https://github.com/radius-project/docs/pull/2041.

Additional context

The original false-green run is https://github.com/radius-project/docs/actions/runs/38964910127/job/117188865986.

Lenguaje dominante
Bicep
Estrellas
27
Forks
51
Merge medio
1 d 8 h
PR fusionados (30 d)
37

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 radius-project/docs

Todos los issues de radius-project/docs

Issues similares

Más issues de DevOps

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.