Port Validation

The validate-ports.sh script detects port drift across three layers of the platform, ensuring that scripts/config/components.yaml remains the single source of truth for all service ports.

Source: scripts/tools/validate-ports.sh

Usage

# Full validation across all layers
./scripts/tools/validate-ports.sh
 
# Validate specific layers
./scripts/tools/validate-ports.sh --layer1    # Helm vs components.yaml
./scripts/tools/validate-ports.sh --layer2    # Script registries vs components.yaml
./scripts/tools/validate-ports.sh --layer3    # Frontend configs vs components.yaml
./scripts/tools/validate-ports.sh --ips       # Stale hardcoded IP detection

Validation Layers

Layer 1: Helm Values vs components.yaml

Compares service ports defined in Helm values.yaml files with the ports registered in components.yaml:

Layer 2: Script Registries vs components.yaml

Checks that port references in build scripts, deployment scripts, and health check scripts match components.yaml:

Layer 3: Frontend Configs vs components.yaml

Validates that frontend API client configurations match the expected backend ports:

Stale IP Detection

Searches for hardcoded IP addresses that may be stale:

Output Format

  ai-service               8000     == 8000     PASS
  tenant-service           8082     == 8082     PASS
  billing-service          8087     != 8088     FAIL

Exit Codes

CI Integration

This tool is designed for CI pipeline integration. Add to your CI workflow:

- name: Validate port consistency
  run: ./scripts/tools/validate-ports.sh

Related Pages

• Core Libraries -- ports.sh library
• Stage 18: Validation -- Deployment validation
• Build System -- Build configuration