You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 25, 2020. It is now read-only.
Thank you for sharing this git repository! While running the "docker-compose -f deploy/gke/docker-compose-gke.yml up" command, I hit upon the above mentioned error complaining there is no access to my current project on the part of the service account.
I went on to check that the service account indeed has the access.
yields
ROLE
roles/cloudsql.admin (I added this to see if it makes any difference.)
roles/owner
Could you please advise what could it have possibly gone wrong?
The text was updated successfully, but these errors were encountered:
kenhglee
changed the title
ERROR: (gcloud.sql.instances.create) User [[email protected]] does not have permission to access project XXX
ERROR: (gcloud.sql.instances.create) User [[email protected]] does not have permission to access project XXX
Oct 6, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi!
Thank you for sharing this git repository! While running the "docker-compose -f deploy/gke/docker-compose-gke.yml up" command, I hit upon the above mentioned error complaining there is no access to my current project on the part of the service account.
I went on to check that the service account indeed has the access.
gcloud projects get-iam-policy XXX
--flatten="bindings[].members"
--format='table(bindings.role)'
--filter="bindings.members:[email protected]"
yields
ROLE
roles/cloudsql.admin (I added this to see if it makes any difference.)
roles/owner
Could you please advise what could it have possibly gone wrong?
The text was updated successfully, but these errors were encountered: