我在firebase CLI中部署云功能时遇到问题。我从github克隆了“functions-samples”repo，然后在这个repo的“quickstarts / big-ben”项目中运行了deploy命令。 我按照说明运行了以下命令：
cd functions
npm install
cd ..
firebase deploy
之后，我在我的电源外壳中得到了这个输出
=== Deploying to 'fire-campus'...
i deploying functions, hosting
i functions: ensuring necessary APIs are enabled...
i runtimeconfig: ensuring necessary APIs are enabled...
+ runtimeconfig: all necessary APIs are enabled
! functions: missing necessary APIs. Enabling now...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
i functions: waiting for APIs to activate...
Error: Timed out waiting for APIs to enable. Please try again in a few minutes.
我在谷歌云平台 - Firebase Remote Congig API，Firebase Rules API，Google Cloud RuntimeConfig API中启用了这些API。
我还需要启用哪些来激活firebase CLI中所需的API？ 我需要注册谷歌云功能吗？我没有在注册表单中提供的付款选项。
答案 0 :(得分：2)
两天后问题自动解决了。可能这是一个暂时的问题。无需在Google云平台上注册Google云端功能。我猜这个服务与firebase云功能无关。
答案 1 :(得分：1)
我有同样的问题。我只是在终端中使用了以下代理：
export http_proxy=YOUR_PROXY
export https_proxy=YOUR_PROXY
之后就解决了问题。请注意，您的代理服务器应该是http（s），并且袜子不起作用。