在 Blitz.js api 处理程序中运行时，Google Cloud Storage 调用失败并显示“error:0909006C:PEM routines:get_name:no start line”

Question

当我尝试在Blitz.js /api 处理程序中使用@google-cloud/storage时，它会生成此错误：

error:0909006C:PEM routines:get_name:no start line
    at Sign.sign (internal/crypto/sig.js:110:29)
    at NodeCrypto.sign (C:\Users\markj\workspace\myapp\node_modules\google-auth-library\build\src\crypto\node\crypto.js:35:23)
    at GoogleAuth.sign (C:\Users\markj\workspace\myapp\node_modules\google-auth-library\build\src\auth\googleauth.js:561:39)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async sign (C:\Users\markj\workspace\myapp\node_modules\@google-cloud\storage\build\src\signer.js:174:35) {
  name: 'SigningError'

但是，当我使用node test_api.js在本地运行它时，它工作正常......

这是我的代码：

// test_api.js

const {Storage} = require('@google-cloud/storage');

const client_id = process.env.GCP_STORAGE_ADMIN_CLIENT_ID
const projectId = process.env.GCP_PROJECT_ID
const client_email = process.env.GCP_STORAGE_ADMIN_CLIENT_EMAIL
const private_key = process.env.GCP_STORAGE_ADMIN_PRIVATE_KEY

const storage = new Storage({
    projectId,
    credentials: {
        client_id,
        client_email,
        private_key,
    }
});

async function listBuckets() {
    console.log('PRIVATE KEY: ', private_key) // the error seems to indicate there is an issue here
    // Output: "-----BEGIN PRIVATE KEY-----\n[the private key]\n-----END PRIVATE KEY-----\n"
    const [buckets] = await storage.getBuckets();
    console.log('Buckets:');
    buckets.forEach(bucket => {
      console.log(bucket.name);
    });
}

module.exports = {
    listBuckets // this function errors when called within Next.js /api handler
}

// When I uncomment this and run the file directly with node, it works
// listBuckets()

该错误似乎表明我的私钥的开始/前缀有问题，但我从 Google 服务帐户 JSON 文件中准确复制了它。 它看起来像这样：

-----BEGIN PRIVATE KEY-----\n[the private key]\n-----END PRIVATE KEY-----\n

Answer 1

原来是我的.env.local环境变量中错位的尾随逗号。

GCP_STORAGE_ADMIN_PRIVATE_KEY="[the private key]",

尾随的逗号不明显，因为我关闭了自动换行，并且 console.logs 没有显示逗号，但它以某种方式读取了逗号并导致整个私钥被错误地解析。