了解“需要采取的行动"；来自GCP的电子邮件，重新:启用Cloud Build API [英] understanding "action required" email from GCP, re: enable Cloud Build API

问题描述

我将Firebase用于我的Web应用程序，而不是Google Cloud Platform，尽管我知道在幕后，每个Firebase项目也是一个GCP项目.

I use Firebase for my web apps, not Google Cloud Platform -- though I'm aware that behind the scenes, every Firebase project is also a GCP project.

我刚从GCP收到一封电子邮件，说(摘录):

I just received an email from GCP, saying (excerpted):

[需要采取的措施]:在2020年4月20日之前为您的项目启用Cloud Build API，以确保正确构建和部署Cloud Function ...您必须为您的项目启用Cloud Build API，以确保您的项目Cloud Function已正确构建和部署.启用API后，如果您的Cloud Build，Container Registry或Cloud Storage的使用量超出了这些产品的免费套餐限制，则可能会产生费用.

[Action required]: Enable the Cloud Build API for your projects before April 20, 2020, to ensure Cloud Function is built and deployed correctly ... You must enable the Cloud Build API for your project(s) to ensure your Cloud Function is built and deployed correctly. Once you enable the API, you may incur charges if your Cloud Build, Container Registry, or Cloud Storage usage exceeds the free tier limits for these products.

这是否会完全影响Firebase的部署或开发过程?(例如，现在我使用firebase deploy)

Does this impact the deployment or development process for Firebase at all? (e.g., right now I use firebase deploy )

据我所知，答案是否定的-它只是允许更长的每天最大构建时间.但是电子邮件中根本没有提到Firebase，因此我想确保我在4月20日之前完全了解其他任何含义.

As far as I can tell, the answer is no -- it just allows for a greater maximum build-time-per-day. But the email didn't mention Firebase at all, so I want to be sure I understand any other implications well before April 20.

推荐答案

我有相同的问题并与Firebase支持团队联系，这是我的问题和得到的答案:

I had the same questions and got in touch with the firebase support team, here are my questions and the answers I received:

这是强制性的吗?"

仅当您将来要部署云功能时， 部署的功能不会受到影响.

Only if you are going to deploy Cloud Functions in the future, already deployed functions will not be affected.

我如何知道我的Cloud Build，Container Registry或Cloud Storage的使用量是否会超过这些产品的免费套餐限制?有什么方法可以检查我一直在使用的内容，以便为我做好准备吗? "

"How do I know if my Cloud Build, Container Registry, or Cloud Storage usage will exceed the free tier limits for these products? is there any way how can check what I've been using so I'll be prepared?"

Cloud Build提供了一个免费层，其中只有超过120的使用量 每天将收取构建时间/天.免费使用时 层，则不会向您收取Cloud的Cloud Build部分的费用 功能部署.有关更多信息，请参见Cloud Build定价. 同样，云存储和容器注册表共享免费层 仅收取超过5GB月的使用费. (*注:免费 仅限于美国地区-US-WEST1，US-CENTRAL1和US-EAST1 并汇总到所有3个区域)?例如，如果您有一个大 部署使用100GB存储空间的用户，则只需向您收取 每月需另外支付$ 2.47的存储费用(根据这些特定的美国 区域存储价格).您可以监控使用情况，并查看是否 您即将达到免费配额.

Cloud Build provides a free tier where only usage above 120 build-minutes/day will be charged. When your usage is within the free tier, you will not be charged for the Cloud Build portion of Cloud Function deployments. See Cloud Build pricing for more information. Similarly, Cloud Storage and Container Registry share a free tier where only usage above 5GB-months will be charged. ( * Note : free tier only limited to US regions - US-WEST1, US-CENTRAL1, and US-EAST1 and aggregated over all 3 regions )? For example, if you have a large deployment that uses 100GB of storage, you will only be charged an additional $2.47 for storage/month (based on these particular U.S. regional storage prices). You can monitor your usage and see whether you are getting close to hitting the free quotas.

最后，所有这些东西对我的应用程序有什么作用?为什么我需要添加其他功能?如果要卖给我，您将如何在我的用例中展示它?"

"Lastly, what does all this stuff do for my app? Why do I need to add this other features? If you were to sell me this, how would you present it for my use-case?"

这是Google尽最大努力传达的信息， 用户继续使用该产品所必需的 被认为是必要的法律更新，并且使客户远离 有未来的问题.使用Cloud Build，Container Registry和Cloud 存储具有以下好处:详细的功能构建日志 将可在GCP控制台中使用，以帮助调试和 提高知名度.获得超过构建时间的能力 当前的构建配额为每天120个构建分钟.查看已建项目的能力 您在Container Registry中使用的功能的容器映像.

This is a best effort from Google to communicate information that is necessary to the user’s continued use of the product or that is considered a necessary legal update and keep customers away from having future issues. Using Cloud Build, Container Registry and Cloud Storage provides the following benefits: Detailed function build logs will be available in the GCP Console, aiding in debugging and increasing visibility. The ability to get build time that exceeds the current build quota of 120 build-mins/day. The ability to view a built container image for your function in Container Registry.

这篇关于了解“需要采取的行动"；来自GCP的电子邮件，重新:启用Cloud Build API的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！