debug: GCP Functions - try Node.js v18 and 3.0.x-tls

[Jolg42]

No description provided.

[Jolg42]

The test actually errors because the expectation will need to be updated. But I consider it a successful deployment.

We can see in the logs that the binaryTarget switched, liked expected from libquery_engine-debian-openssl-1.0.x.so.node to libquery_engine-debian-openssl-3.0.x.so.node
https://github.com/prisma/ecosystem-tests/actions/runs/7419853544/job/20190158501?pr=4433#step:8:4154

See function
https://us-central1-prisma-e2e-tests-265911.cloudfunctions.net/e2e-test-2024-01-05-090416

[Jolg42]

I pushed a copy of the debian-bullseye-amd64-openssl-1.1.x-tls test and modified it as debian-latest-amd64-openssl-3.0.x-tls
Because it’s testing Prisma Client using GCP Postgres with the SSL certificate.

And I can reproduce what was mentioned in prisma/prisma#22520
Logs

PrismaClientInitializationError: 
Invalid `client.user.findMany()` invocation in
/usr/src/app/server.js:12:34

   9 const client = new PrismaClient()
  10 
  11 app.get('/', async (req, res) => {
→ 12   const data = await client.user.findMany(
Error opening a TLS connection: error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:../crypto/evp/evp_fetch.c:373:Global default library context, Algorithm (RC2-40-CBC : 0), Properties ()
    at si.handleRequestError (/usr/src/app/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client/runtime/library.js:125:7117)
    at si.handleAndLogRequestError (/usr/src/app/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client/runtime/library.js:125:6151)
    at si.request (/usr/src/app/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client/runtime/library.js:125:5859)
    at async l (/usr/src/app/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client/runtime/library.js:130:9805)
    at async /usr/src/app/server.js:12:16 {
  clientVersion: '5.8.0-dev.50',
  errorCode: undefined
}