Add Health Check Endpoint

[Yash Shrivastava (alephys26)]

Background

We did not have health checks for the clusters in Heimdall. Introducing health check endpoints for greater observability. The health checks are set on clusters (with opt-in) and run only if there is at least a single command that uses the cluster.

Changes

• Cluster Health Check System

  • Introduced a configurable, concurrent health check system with new API endpoints for checking cluster health, and updated the main Heimdall struct and router to support it. [1] [2] [3]
  • Added cluster-level opt-in for health checks and global timeout configuration in local.yaml. [1] [2]

• Plugin Health Check Implementations

  • Implemented lightweight HealthCheck methods in ClickHouse, DynamoDB, ECS Fargate, Glue, Ping, Postgres, Shell, and Snowflake plugins for backend connectivity probing. [1] [2] [3] [4] [5] [6] [7] [8]

• Documentation and Configuration

  • Updated README.md to document cluster health checks, endpoints, configuration, and plugin support. [1] [2] [3]
  • Added new plugins to the supported plugins table (sparkeks, postgres).

• Dependency Updates

  • Upgraded AWS SDK and related dependencies in go.mod for compatibility with health check implementations. [1] [2]

Tests

Tested with go test files. All unit tests passed.
Also tested locally with docker compose.

[wiz-55ccc8b716]

Wiz Scan Summary

Scanner	Findings
Vulnerabilities	-
Sensitive Data	-
Secrets	-
IaC Misconfigurations	-
SAST Findings	4  1
Software Management Findings	-
Total	4  1

View scan details in Wiz

To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension.