meldestelle/.junie/scripts/validate-links.sh
StefanMo b35c4087a2
Fix: Test-Commit für VCS-Integration (MP-8) (#15)
* MP-8 OTHER Implementiere JWT-Authentifizierungs-Filter im Gateway

* Fix(ci): Update upload-artifact action to v4

* Fix(ci): Add start command for Keycloak and failure logs

* Fix(ci): Remove invalid 'command' property from Keycloak service

* Fix(ci): Use KC_DEV_MODE env var to start Keycloak

* Fix(ci): Keycloak service was removed from GitHub Actions services and replaced with a manual docker run step that starts Keycloak with the start-dev command.

* dev(ci): vereinheitliche Keycloak auf 26.4.2; aktiviere Health im CI (MP-8)

* Fix(ci): Stabilize Keycloak startup in integration tests via matrix

- Add `dev-file` Keycloak variant to matrix for stability fallback.
- Improve wait logic and health checks for Keycloak and Postgres.
- Unify Keycloak version to 26.4.2 across codebase.
- Add log dumps on failure.

* Fix(ci): Die betroffene Datei docs/Visionen-Ideen/Infrastruktur-Strategie_DSGVO-Konformität.md endet aktuell mit genau einer leeren Zeile (Zeile 87). Das entspricht der Regel MD047 („Files should end with a single newline character“). Damit ist deine Korrektur korrekt.

* Fix(ci): Repository-wide auto-fix for Markdown files was implemented with a GitHub Actions workflow and a local helper script. EditorConfig and markdownlint ignore files were added to ensure consistent formatting. Instructions for using the auto-fix both via GitHub Actions and locally were provided.

* fix(gradle): build.gradle.kts jsBrowser testTask disabled

* fix(gradle): build.gradle.kts jsBrowser testTask disabled

* Fix(ci): Stabilize integration tests with Keycloak matrix build (MP-8)

Introduces a matrix strategy (`keycloak_db: [postgres, dev-file]`)
in the integration-tests workflow to mitigate flaky Keycloak starts
when using the Postgres service container.

- Adds a `dev-file` Keycloak variant for stability fallback.
- Improves wait logic and health checks for Keycloak/Postgres.
- Unifies Keycloak version to 26.4.2 across codebase (Dockerfile, Compose,
  ADR, README, tests).
- Adds log dumps on failure in CI.
- Ensures `KC_HEALTH_ENABLED=true` is set.
- Updates related documentation (README, Schlachtplan).
- Includes broader Docker SSoT cleanup (versions.toml as source,
  script updates, env file cleanup, validator hardening).

This resolves recurring CI failures related to Keycloak startup and
ensures required checks for PRs (#15) are reliable, while also
improving overall Docker build consistency.

* feat(docs, ci): Implement YouTrack SSoT strategy with Dokka sync (MP-8)

- Add Dokka multi-module Gradle configuration and KDoc style guide.
- Add GitHub Actions workflow (docs-kdoc-sync.yml) and Python script
  (youtrack-sync-kb.py) to sync Dokka GFM output to YouTrack KB.
- Extend front-matter schema (bc, doc_type) and update relevant pages/stubs.
- Adapt CI scripts (validate-frontmatter, check-docs-drift, ci-docs link ignore).
- Update README.md to reference YouTrack KB.

* feat(docs, ci): Implement YouTrack SSoT strategy with Dokka sync (MP-8)

- Add Dokka multi-module Gradle configuration and KDoc style guide.
- Add GitHub Actions workflow (docs-kdoc-sync.yml) and Python script
  (youtrack-sync-kb.py) to sync Dokka GFM output to YouTrack KB.
- Extend front-matter schema (bc, doc_type) and update relevant pages/stubs.
- Adapt CI scripts (validate-frontmatter, check-docs-drift, ci-docs link ignore).
- Update README.md to reference YouTrack KB.

* Fix(ci): Replace OpenAPI validator with Spectral

Replaces the deprecated 'char0n/swagger-editor-validate' action,
which failed due to sandbox issues in GitHub Actions, with the
modern '@stoplight/spectral-cli'.

This ensures robust OpenAPI specification validation without
requiring a headless browser environment. The 'generate-api-docs'
job now depends on the successful completion of the Spectral validation.

Part of resolving CI failures for PR #15 (MP-8).

* Fix(ci): Specify spectral:oas ruleset for OpenAPI validation (MP-8)

* Fix(ci): Remove explicit ruleset argument for Spectral validation (MP-8)

* Fix(ci): Added a .spectral.yaml file to fix Spectral linting errors. Corrected markdown lint issues in two documentation files. Updated README.md with a new guidelines section to fix link validation errors.

* Fix(ci): Markdownlint errors were fixed by adding required blank lines. The Guidelines Validation error was resolved by updating the README.md link. The API Documentation Generator workflow was stabilized by updating paths, tasks, and validation steps.

* Fix(ci): Alle vier fehlerhaften GitHub-Action-Prüfungen wurden behoben. Fehler in der OpenAPI-Spezifikation, Probleme mit der Markdown-Linting-Analyse und Validierungsfehler bei Querverweisen wurden korrigiert. Die README.md enthält nun alle erforderlichen Links zu den Richtlinien.

* Fix(ci): Markdown linting errors in docs/api/README.md were fixed by specifying languages in fenced code blocks. OpenAPI specification errors in documentation.yaml were resolved by correcting example property types to strings. Cross-reference validation errors in README.md were fixed by adding the missing link to project-standards/coding-standards.md.

* Fix(ci): Duplicate heading errors in docs/api/members-api.md were fixed. Cross-reference validation errors for docker-architecture.md were resolved. All originally reported issues passed validation successfully.

* Fix(ci): The markdown heading levels in docs/api/members-api.md were corrected from h5 to h4 to fix linting errors. The missing cross-reference link from technology-guides/docker/docker-development.md to docker-overview.md was added. These fixes resolved the original validation and linting errors causing the process to fail.

* Fix(ci): Duplicate heading warnings in docs/api/members-api.md were resolved. Cross-reference validation for docker-development.md to docker-architecture.md was fixed. A new unrelated warning about docker-production.md was identified but not addressed.

* refactor(ci,docs): Simplify CI pipeline and migrate docs to YouTrack SSoT

BREAKING CHANGE: Documentation structure radically simplified

- Consolidate 9 GitHub Actions workflows into 1 main pipeline (ci-main.yml)
- Remove redundant workflows: ci-docs, markdownlint-autofix, guidelines-validation, api-docs
- Delete documentation migrated to YouTrack: api/, BCs/, Visionen-Ideen/, reference/, now/, overview/
- Keep only ADRs, C4 diagrams, and essential dev guides in repo
- Update README.md with YouTrack KB links
- Create new docs/README.md as documentation gateway
- Relax markdown-lint config for pragmatic developer experience

Kept workflows:
- ssot-guard.yml (Docker SSoT validation)
- docs-kdoc-sync.yml (KDoc → YouTrack sync)
- integration-tests.yml (Integration tests)
- deploy-proxmox.yml (Deployment)
- youtrack-sync.yml (YouTrack integration)

Related: MP-DOCS-001

* refactor(ci,docs): Simplify CI pipeline and migrate docs to YouTrack SSoT

BREAKING CHANGE: Documentation structure radically simplified

- Consolidate 9 GitHub Actions workflows into 1 main pipeline (ci-main.yml)
- Remove redundant workflows: ci-docs, markdownlint-autofix, guidelines-validation, api-docs
- Delete documentation migrated to YouTrack: api/, BCs/, Visionen-Ideen/, reference/, now/, overview/
- Keep only ADRs, C4 diagrams, and essential dev guides in repo
- Update README.md with YouTrack KB links
- Create new docs/README.md as documentation gateway
- Relax markdown-lint config for pragmatic developer experience

Kept workflows:
- ssot-guard.yml (Docker SSoT validation)
- docs-kdoc-sync.yml (KDoc → YouTrack sync)
- integration-tests.yml (Integration tests)
- deploy-proxmox.yml (Deployment)
- youtrack-sync.yml (YouTrack integration)

Related: MP-DOCS-001

* refactor(ci,docs): README.md und einige andere Dokumentationen überarbeitet.
ports-and-urls.md hinzugefügt.
Related: MP-DOCS-001

* refactor(ci,docs): Die Markdownlint-Fehler in README.md und docs/README.md wurden behoben, indem die Überschriftenebenen angepasst, überflüssige Satzzeichen am Ende entfernt und die notwendigen Leerzeilen um Überschriften, Listen, Tabellen und Codeblöcke eingefügt wurden. Das problematische Leerzeichen am Ende in docs/README.md wurde ebenfalls entfernt. Die Dateien entsprechen nun den vorgegebenen Markdownlint-Regeln und sollten die CI-Validierung bestehen.
Related: MP-DOCS-001

* refactor(ci,docs): Docker guideline cross-references were fixed and normalized to lowercase labels. Validation scripts confirmed zero cross-reference warnings and consistent metadata. Documentation was updated with a changelog and enhanced README navigation.
Related: MP-DOCS-001

* refactor(ci,docs): Docker guideline cross-references were fixed and normalized to lowercase labels. Validation scripts confirmed zero cross-reference warnings and consistent metadata. Documentation was updated with a changelog and enhanced README navigation.
Related: MP-DOCS-001

* refactor(ci,docs): Dead links in docs/architecture/adr were fixed by updating URLs to stable sources and adding an ignore pattern for a placeholder link. Specific ADR files had their broken links replaced with valid ones. The markdown-link-check GitHub Action is expected to pass with zero dead links now.
Related: MP-DOCS-001

* refactor(ci,docs): Links in ADR checked
Related: MP-DOCS-001

* refactor(ci,docs): Links in ADR checked
Related: MP-DOCS-001

* refactor(ci,docs): Markdown Regeln ausgebessert
Related: MP-DOCS-001

* refactor(ci,docs): Markdown Regeln ausgebessert
Related: MP-DOCS-001

* refactor(ci,docs): Markdown Regeln ausgebessert
Related: MP-DOCS-001

* Chore: Rerun CI checks with updated branch protection rules
2025-11-07 12:26:33 +01:00

344 lines
11 KiB
Bash
Executable File
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

#!/bin/bash
# validate-links.sh - Automatisierte Link-Validierung für Meldestelle Guidelines
# Version: 1.0.0
# Autor: Junie AI-Assistant
# Datum: 2025-09-15
set -euo pipefail
# Bestimme das Projekt-Root-Verzeichnis
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
PROJECT_ROOT="$(cd "$SCRIPT_DIR/../.." && pwd)"
# Wechsle ins Projekt-Root für korrekte relative Pfade
cd "$PROJECT_ROOT"
GUIDELINES_DIR=".junie/guidelines"
META_DIR="$GUIDELINES_DIR/_meta"
CROSS_REFS_FILE="$META_DIR/cross-refs.json"
SCRIPTS_DIR=".junie/scripts"
# Farben für Output
RED='\033[0;31m'
GREEN='\033[0;32m'
YELLOW='\033[1;33m'
BLUE='\033[0;34m'
NC='\033[0m' # No Color
# Logging-Funktionen
log_info() {
echo -e "${BLUE} $1${NC}"
}
log_success() {
echo -e "${GREEN}$1${NC}"
}
log_warning() {
echo -e "${YELLOW}⚠️ $1${NC}"
}
log_error() {
echo -e "${RED}$1${NC}"
}
# Hauptvariablen
ERRORS=0
WARNINGS=0
QUICK_MODE=false
# Command-line Parameter
while [[ $# -gt 0 ]]; do
case $1 in
--quick)
QUICK_MODE=true
shift
;;
--help|-h)
cat << 'EOF'
Meldestelle Guidelines Link-Validierung
USAGE:
./validate-links.sh [OPTIONS]
OPTIONS:
--quick Schnelle Validierung (nur kritische Checks)
--help Diese Hilfe anzeigen
BESCHREIBUNG:
Validiert alle Links und Cross-Referenzen in den Guidelines basierend auf
der cross-refs.json Matrix. Prüft:
- Cross-Referenzen zwischen Guidelines
- Markdown-Links in Guidelines
- YAML-Metadaten-Konsistenz
- Template-Struktur-Konsistenz
EXIT-CODES:
0 = Alle Validierungen erfolgreich
1 = Fehler gefunden
2 = Warnings gefunden (nur bei --strict)
EOF
exit 0
;;
*)
log_error "Unbekannter Parameter: $1"
echo "Nutze --help für Hilfe"
exit 1
;;
esac
done
echo "🔍 Meldestelle Guidelines Link-Validierung"
echo "=================================================="
echo "Datum: $(date '+%Y-%m-%d %H:%M:%S')"
echo "Modus: $([ "$QUICK_MODE" = true ] && echo "Quick" || echo "Vollständig")"
echo ""
# Prüfe ob erforderliche Dateien existieren
if [[ ! -f "$CROSS_REFS_FILE" ]]; then
log_error "Cross-Referenz-Datei nicht gefunden: $CROSS_REFS_FILE"
exit 1
fi
if [[ ! -d "$GUIDELINES_DIR" ]]; then
log_error "Guidelines-Verzeichnis nicht gefunden: $GUIDELINES_DIR"
exit 1
fi
# 1. Cross-Referenz-Validierung
validate_cross_references() {
log_info "Validiere Cross-Referenzen aus cross-refs.json..."
local temp_guidelines=$(mktemp)
local temp_refs=$(mktemp)
# Alle Guidelines aus cross-refs.json extrahieren
jq -r '.cross_references | keys[]' "$CROSS_REFS_FILE" > "$temp_guidelines" 2>/dev/null || {
log_error "Fehler beim Lesen der cross-refs.json"
((ERRORS++))
return
}
while IFS= read -r guideline; do
# Special handling for README.md which is at project root
if [[ "$guideline" == "README.md" ]]; then
guideline_file="$PROJECT_ROOT/README.md"
else
guideline_file="$GUIDELINES_DIR/$guideline"
fi
# Prüfe ob Guideline-Datei existiert
if [[ ! -f "$guideline_file" ]]; then
log_error "Guideline '$guideline' in cross-refs.json aber Datei fehlt: $guideline_file"
((ERRORS++))
continue
fi
# Hole referenzierte Guidelines aus JSON
jq -r ".cross_references[\"$guideline\"].references_to[]? // empty" "$CROSS_REFS_FILE" > "$temp_refs" 2>/dev/null
while IFS= read -r ref; do
# Skip leere Zeilen
[[ -z "$ref" ]] && continue
# Relativer Pfad zu absolut konvertieren
if [[ "$ref" == /* ]]; then
ref_file="$GUIDELINES_DIR$ref"
elif [[ "$ref" == *"/" ]]; then
# Directory-Referenz (z.B. technology-guides/docker/)
ref_dir="$GUIDELINES_DIR/$ref"
if [[ ! -d "$ref_dir" ]]; then
log_error "Referenziertes Verzeichnis '$ref' existiert nicht: $ref_dir"
((ERRORS++))
fi
continue
else
# Alle Referenzen sind relativ zum Guidelines-Root-Verzeichnis
ref_file="$GUIDELINES_DIR/$ref"
fi
# Normalisiere Pfad
ref_file=$(realpath -m "$ref_file" 2>/dev/null || echo "$ref_file")
# Prüfe ob referenzierte Datei existiert
if [[ ! -f "$ref_file" ]]; then
log_error "'$guideline' referenziert '$ref', aber Datei existiert nicht: $ref_file"
((ERRORS++))
continue
fi
# Prüfe ob der Link tatsächlich im Markdown existiert (nur im vollständigen Modus)
if [[ "$QUICK_MODE" = false ]]; then
ref_basename=$(basename "$ref" .md)
# Check for link with basename in brackets OR reference path (with or without directory) in parentheses
if ! grep -q "\[$ref_basename\]" "$guideline_file" && ! grep -qE "\([^)]*$ref\)" "$guideline_file"; then
log_warning "'$guideline' sollte '$ref' referenzieren, aber Link fehlt im Markdown"
((WARNINGS++))
fi
fi
done < "$temp_refs"
log_success "'$guideline' - Cross-Referenzen validiert"
done < "$temp_guidelines"
rm -f "$temp_guidelines" "$temp_refs"
}
# 2. Markdown-Links Validierung
validate_markdown_links() {
if [[ "$QUICK_MODE" = true ]]; then
log_info "Überspringe Markdown-Link-Validierung (Quick-Modus)"
return
fi
log_info "Validiere Markdown-Links in Guidelines..."
find "$GUIDELINES_DIR" -name "*.md" -not -path "*/_archived/*" | while read file; do
# Relative Links extrahieren ([Text](./path/file.md))
grep -o "\[.*\](\./[^)]*\.md)" "$file" 2>/dev/null | sed 's/.*(\.\///' | sed 's/).*//' | while read link; do
[[ -z "$link" ]] && continue
# Absoluten Pfad konstruieren
dir=$(dirname "$file")
target_file="$dir/$link"
target_file=$(realpath -m "$target_file" 2>/dev/null || echo "$target_file")
if [[ ! -f "$target_file" ]]; then
log_error "$(basename "$file") verlinkt auf '$link', aber Ziel existiert nicht: $target_file"
((ERRORS++))
fi
done
# Relative Links mit ../ extrahieren
grep -o "\[.*\](\.\./[^)]*\.md)" "$file" 2>/dev/null | sed 's/.*(\.\.\///' | sed 's/).*//' | while read link; do
[[ -z "$link" ]] && continue
dir=$(dirname "$file")
target_file="$dir/../$link"
target_file=$(realpath -m "$target_file" 2>/dev/null || echo "$target_file")
if [[ ! -f "$target_file" ]]; then
log_error "$(basename "$file") verlinkt auf '../$link', aber Ziel existiert nicht: $target_file"
((ERRORS++))
fi
done
log_success "$(basename "$file") - Markdown-Links validiert"
done
}
# 3. YAML-Metadaten Validierung
validate_yaml_metadata() {
log_info "Validiere YAML-Metadaten-Konsistenz..."
find "$GUIDELINES_DIR" -name "*.md" -not -path "*/_archived/*" -not -name "README.md" -not -name "master-guideline.md" | while read file; do
# YAML-Header extrahieren (nur zwischen den ersten beiden --- Zeilen)
yaml_content=$(awk '/^---$/{if(++count==2) exit} count==1 && !/^---$/{print}' "$file" 2>/dev/null || echo "")
if [[ -z "$yaml_content" ]]; then
log_warning "'$(basename "$file")' hat keinen YAML-Header"
((WARNINGS++))
continue
fi
# YAML-Syntax prüfen (falls python verfügbar)
if command -v python3 &> /dev/null; then
echo "$yaml_content" | python3 -c "import yaml,sys; yaml.safe_load(sys.stdin)" 2>/dev/null || {
log_error "'$(basename "$file")' hat ungültige YAML-Syntax im Header"
((ERRORS++))
continue
}
fi
# Erforderliche Felder prüfen
required_fields=("guideline_type" "scope" "audience" "last_updated" "ai_context")
for field in "${required_fields[@]}"; do
if ! echo "$yaml_content" | grep -q "^$field:" 2>/dev/null; then
log_error "'$(basename "$file")' fehlt erforderliches YAML-Feld: $field"
((ERRORS++))
fi
done
# Dependencies validieren (nur im vollständigen Modus)
if [[ "$QUICK_MODE" = false ]]; then
deps=$(echo "$yaml_content" | grep "dependencies:" 2>/dev/null | sed 's/.*\[//' | sed 's/\].*//' | tr ',' '\n' | sed 's/[" ]//g' || echo "")
for dep in $deps; do
[[ -z "$dep" ]] && continue
dep_file="$GUIDELINES_DIR/$dep"
if [[ ! -f "$dep_file" ]]; then
log_error "'$(basename "$file")' dependency '$dep' existiert nicht"
((ERRORS++))
fi
done
fi
log_success "$(basename "$file") - Metadaten validiert"
done
}
# 4. Template-Struktur Validierung
validate_template_structure() {
if [[ "$QUICK_MODE" = true ]]; then
log_info "Überspringe Template-Validierung (Quick-Modus)"
return
fi
log_info "Validiere Template-Struktur-Konsistenz..."
local template_dir="$GUIDELINES_DIR/_templates"
if [[ ! -d "$template_dir" ]]; then
log_warning "Template-Verzeichnis nicht gefunden: $template_dir"
((WARNINGS++))
return
fi
# Prüfe ob neue Guidelines Template-Struktur folgen
find "$GUIDELINES_DIR" -name "*.md" -not -path "*/_archived/*" -not -path "*/_templates/*" -not -name "README.md" | while read file; do
# Prüfe grundlegende Template-Struktur
if ! grep -q "^guideline_type:" "$file" 2>/dev/null; then
log_warning "'$(basename "$file")' folgt möglicherweise nicht der Template-Struktur (fehlt guideline_type)"
((WARNINGS++))
fi
if ! grep -q "^ai_context:" "$file" 2>/dev/null; then
log_warning "'$(basename "$file")' folgt möglicherweise nicht der Template-Struktur (fehlt ai_context)"
((WARNINGS++))
fi
done
log_success "Template-Struktur validiert"
}
# Hauptvalidierung ausführen
main() {
validate_cross_references
validate_markdown_links
validate_yaml_metadata
validate_template_structure
echo ""
echo "=================================================="
echo "📊 Validierungs-Ergebnisse:"
echo " Fehler: $ERRORS"
echo " Warnungen: $WARNINGS"
if [[ $ERRORS -eq 0 && $WARNINGS -eq 0 ]]; then
log_success "Alle Validierungen erfolgreich! 🎉"
exit 0
elif [[ $ERRORS -eq 0 ]]; then
log_warning "Validierung abgeschlossen mit $WARNINGS Warnungen"
exit 0
else
log_error "Validierung fehlgeschlagen mit $ERRORS Fehlern und $WARNINGS Warnungen"
exit 1
fi
}
# Script ausführen
main "$@"