ci-smoke-needs-real-deps

CI smoke tests fail because external dependencies like PostgreSQL, MySQL, Redis, MongoDB, or S3 are not available in the test environment. You must declare these dependencies as CI service containers and inject matching environment variables into the smoke step to mirror actual deployment.

To add PostgreSQL and Redis service containers to GitHub Actions smoke tests, update your release CI configuration to declare the required services. Match the environment variables on the smoke step to align ci.yml with release.yml configuration parity.

Aligning ci.yml and release.yml requires a diagnostic checklist to ensure the smoke workflow uses the same service containers and environment variables as the production flow. Apply this pattern during stack migrations or new external service integrations to restore configuration parity.

Yes, this approach applies to GitHub Actions release workflows during dependency migrations, stack upgrades, or when adding new external services. It enforces a pattern of aligning ci.yml and release.yml with diagnostic checks and example snippets for adding services like postgres or redis.

Environment variables must be injected on the smoke step to mirror the actual deployment configuration. Mismatched or missing environment variables cause smoke tests to fail because the test environment cannot locate the external dependencies declared as service containers.

Yes, the service container pattern supports adding MongoDB, S3, PostgreSQL, MySQL, and Redis to GitHub Actions. Declare the required external dependency as a CI service container and inject the matching environment variables on the smoke step to resolve missing dependency failures.