CircleCI 工作流程找不到 Firebase 项目：项目选择无效，请验证项目“项目”；存在并且您有权访问

发布于 2025-01-11 01:23:26 字数 1053 浏览 0 评论 0 原文

我们有一个循环工作流程，每当我们合并到 main 时，它都会自动将我们的 web 应用程序部署到生产环境中。但是，自从将 firebase-tools 更新到 V10.2.1 以来，每当我们尝试将 env-config 设置为“生产”时，我们都会收到以下消息。

> node env-config/env-config "production"

它在底层运行 firebase use production 命令。返回以下错误时，

Error: Command failed: firebase use production
    at ChildProcess.exithandler (child_process.js:383:12)
    at ChildProcess.emit (events.js:400:28)
    at maybeClose (internal/child_process.js:1058:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5) {
  killed: false,
  code: 1,
  signal: null,
  cmd: 'firebase use production',
  stdout: '\n' +
    '\x1B[1m\x1B[31mError:\x1B[39m\x1B[22m Invalid project selection, please verify project \x1B[1mproduction\x1B[22m exists and you have access.\n',
  stderr: ''
}

现在出现了奇怪的部分：在同一工作流程中，它还运行 firebase use test 和 firebase use staging ，两者都按预期工作。在工作流程之外，只需手动运行 firebase use production 也可以按预期工作。有人有建议吗？

原文

We have a circle workflow that automatically deploys our webapp to production for us whenever we merge to main. However, since updating our firebase-tools to V10.2.1 we get the following message whenever we try to set our env-config to "production".

> node env-config/env-config "production"

Under the hood it runs the firebase use production command. Which is when the following error is returned

Error: Command failed: firebase use production
    at ChildProcess.exithandler (child_process.js:383:12)
    at ChildProcess.emit (events.js:400:28)
    at maybeClose (internal/child_process.js:1058:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5) {
  killed: false,
  code: 1,
  signal: null,
  cmd: 'firebase use production',
  stdout: '\n' +
    '\x1B[1m\x1B[31mError:\x1B[39m\x1B[22m Invalid project selection, please verify project \x1B[1mproduction\x1B[22m exists and you have access.\n',
  stderr: ''
}

Now here comes the weird part: in the same workflow it also runs firebase use test and firebase use staging with both work as expected. Outside of the workflow, just manually running firebase use production works as expected as well. Anyone have a suggestion?