Summary
Every BCGov repository currently hand-cranks its own container healthcheck loop using a raw Bash for loop and curl. This is boilerplate-heavy, brittle, and lacks standardized failure telemetry.
The Proposal
We should build bcgov/action-container-smoke-tester as a core, language-agnostic utility in the consolidated re-launch.
Why Container Smoker?
- Language Agnostic: It only cares about the OCI image, not what is running inside.
- Boilerplate Reduction: Replaces 30+ lines of raw Bash with a single, stable action call.
- Standardized Telemetry: Automatically dumps logs, container state, and health diagnosis on failure.
Example V2 Usage:
- uses: bcgov/actions/container-smoke-tester@v1
with:
image: ghcr.io/bcgov/my-app:latest
port: 8080
endpoint: /health
timeout: 60
Summary
Every BCGov repository currently hand-cranks its own container healthcheck loop using a raw Bash
forloop andcurl. This is boilerplate-heavy, brittle, and lacks standardized failure telemetry.The Proposal
We should build bcgov/action-container-smoke-tester as a core, language-agnostic utility in the consolidated re-launch.
Why Container Smoker?
Example V2 Usage: