bug: Staging deploy fails during index step with gRPC/Spanner + OpenSSL "DECODER routines::unsupported"

[isshaddad]

Provide environment information

trigger.dev@latest

Describe the bug

Staging deploy fails during the Docker build index step (managed-index-controller.mjs). The project uses Google Cloud Spanner (or another gRPC/Google client). When the indexer loads the project, gRPC tries to get metadata/credentials and fails with:

Getting metadata from plugin failed with error: error:1E08010C:DECODER routines::unsupported

Stack trace points at @grpc/grpc-js and @google-cloud/spanner. Production deploy with the same code succeeds; only staging fails. Likely an OpenSSL/Node or build-environment difference between staging and production.

Reproduction repo

n/a

To reproduce

1. Create a project that imports or uses @google-cloud/spanner (or another gRPC/Google client).
2. Deploy to staging (e.g. Trigger staging environment).
3. Build fails at index step with the DECODER/grpc-js error above.
4. Deploy the same code to production; build succeeds.

Additional information

• Build log snippet showing the failure is in: RUN node .../managed-index-controller.mjs (indexer step).
• Same code, same trigger.config; only staging fails. Suggests staging vs production build image or env difference.