Connect Cloud Run Functions Reviews

Elena M. · Reviewed about 1 year ago

Kensuke S. · Reviewed about 1 year ago

Dmitriy S. · Reviewed about 1 year ago

AMANDEEP S. · Reviewed about 1 year ago

Jesús V. · Reviewed about 1 year ago

The check my progress for the http-redis function doesn't work

Sam S. · Reviewed about 1 year ago

Thiago S. · Reviewed about 1 year ago

Soyhuce S. · Reviewed about 1 year ago

Juan S. · Reviewed about 1 year ago

Himanshu M. · Reviewed about 1 year ago

Abdulrahaman S. · Reviewed about 1 year ago

Arturo Q. · Reviewed about 1 year ago

Danilo L. · Reviewed about 1 year ago

Leonardo S. · Reviewed about 1 year ago

David Sebastián H. · Reviewed about 1 year ago

Erivelton T. · Reviewed about 1 year ago

Thomas K. · Reviewed about 1 year ago

Denys H. · Reviewed about 1 year ago

Amit K. · Reviewed about 1 year ago

상배 윤. · Reviewed about 1 year ago

In task 6, after disabling and re-enabling the Cloud Functions API, a permissions issue other than the one expected occurred. The gcf-admin-robot service account failed to get recreated when re-enabling the Cloud Functions API, causing an error message stating that the account was deleted whenever attempting to deploy. This did not solve itself for over 5 minutes. Upon rerunning the commands to disable then re-enable the Cloud Functions API, this issue vanished and a non-deleted gcf-admin-robot service account appeared in the IAM page. The permissions issue called out by the instructions did occur at this point (access to Artifact Registry), but this resolved itself shortly as expected.

Maxwell L. · Reviewed about 1 year ago

Aayush D. · Reviewed about 1 year ago

Varun B. · Reviewed about 1 year ago

Esmaeil Z. · Reviewed about 1 year ago

Deepi A. · Reviewed about 1 year ago