I’m not sure why this happens and why this is not clearly stated in the docs though. After that, it keeps working, even if the API is disabled. What’s weird here is that it looks like this API should be enabled only for the first deployment to succeed. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry. If we try to run our pipeline without having this API enabled, it will fail with a message similar to this: ERROR: () User (or it may not exist): Cloud Resource Manager API has not been used in project before or it is disabled. The Cloud Resource Manager API “Creates, reads, and updates metadata for Google Cloud Platform resource containers.” - Under the hood, I imagine Google leverages its container infrastructure for running Cloud Functions on top of it and that’s why this API is needed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |