-
Notifications
You must be signed in to change notification settings - Fork 951
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to set the invoker for the IAM policy on the following functions #6017
Comments
I think this issue is still active. |
Seeing the same thing with newly deployed functions |
That is after recent update, if I were correct. |
I think I have found the solution (here)
Now my function is working again. |
I am having the same problem deploying some functions. We use ansible to run automated deployments, which uses a service account for authentication (not "firebase login"). To use a service account key:
Everything was working fine within the last month. New functions were properly deployed. Nothing was changed with out firebase config, only new function code. The workarounds listed above did not work. However, we can login ("firebase login") with a user account and run the deploy successfully. As a small team, it's daunting to manage all this security spaghetti google cloud is throwing at us. |
Thank you @gOzaru! It works for me. I want to share the steps I had to take:
|
[REQUIRED] Environment info
firebase-tools: 12.4.0
Platform: Windows
[REQUIRED] Test case
I can't provide the sample as it is owned by company.
The important thing is that I want to edit the data inside Firestore using Cloud Functions. It used to have no error at all. But, now it gives error:
I logged in as Owner access in Firebase Cloud Function.
This should give me absolute access to all roles.
[REQUIRED] Steps to reproduce
Just deploy function which has editing and deleting data inside Firestore
[REQUIRED] Expected behavior
It should be run without error.
[REQUIRED] Actual behavior
The function cannot be run anymore.
The text was updated successfully, but these errors were encountered: