It's glaringly obvious that a hard cap on the budget is a missing feature, since all projects need to deal with billing. What's even more bizarre, is that Google's docs include a tutorial, with code, on how to set up this feature.
To me, this says that the shortcoming has been noted, and then a product manager has argued against implementation. If I squint I can even justify it - shutting down a website right when it gets hugely popular is not something that's easily reversed, while it's pretty easy for GCP to write off a bill for $1k.
The tutorial's budget hard limit system is actually kinda interesting as it dogfoods GCP - the budget-hit notification is sent via GCP pubsub, and a lambda (aka Google Cloud Function) then removes the billing account from the project, which shuts down the project's resources.
(To be clear, having to write/tweak code and deploy this myself is a suboptimal solution to the problem but it's neat from an engineering perspective.)
To me, this says that the shortcoming has been noted, and then a product manager has argued against implementation. If I squint I can even justify it - shutting down a website right when it gets hugely popular is not something that's easily reversed, while it's pretty easy for GCP to write off a bill for $1k.
The tutorial's budget hard limit system is actually kinda interesting as it dogfoods GCP - the budget-hit notification is sent via GCP pubsub, and a lambda (aka Google Cloud Function) then removes the billing account from the project, which shuts down the project's resources.
https://cloud.google.com/billing/docs/how-to/notify#cap_disa...
(To be clear, having to write/tweak code and deploy this myself is a suboptimal solution to the problem but it's neat from an engineering perspective.)