http-health-smoke

HTTP health checks on multiple endpoints are executed using a Bash script that calls curl to request each path and validate response status codes, verifying service uptime across local development, CI pipelines, and staging environments.

An HTTP smoke test validates service uptime by issuing standard curl requests against configured health and readiness paths, then checking returned status codes to confirm services are operational before gating subsequent deployment steps.

Yes, you can use curl to check health endpoints in a CI pipeline by running a Bash script that fetches each specified path from a base URL and reports basic health based on the received HTTP response status codes.

To validate multiple readiness paths before deployment tests, supply a base URL and specific paths to a Bash health-check script, which uses curl to request each endpoint and gates subsequent tests based on returned status codes.

The best way to gate CI pipelines using HTTP status codes is to run a Bash smoke test that curls configured endpoints, failing the pipeline step if any service returns an invalid status code, thus catching outages before deployment.

No external dependencies are needed to run Bash HTTP health checks beyond standard environment tooling, as the script relies solely on curl and Bash to issue requests and validate the status codes of targeted endpoints.