storage: Service account does not exist.
See original GitHub issueIn Recent All the PR is failing because of below service account:
Error: Exit code: 400
Google.Apis.Requests.RequestError
Service account 230835935096-8io28ro0tvbbv612p5k6nstlaucmhnrq@developer.gserviceaccount.com does not exist. [400]
Errors [
Message[Service account 230835935096-8io28ro0tvbbv612p5k6nstlaucmhnrq@developer.gserviceaccount.com does not exist.] Location[ - ] Reason[invalid] Domain[global]
]
Expected: True
Actual: False
@amanda-tarafa any Idea on this? I think we should store this on environment variable.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Service account does not have storage.buckets.get access ...
The error you're seeing is because the permission storage.buckets.get is missing from the service account -- that is, none of the role(s) ...
Read more >service account does not have storage.objects.get access ...
I have created a service account in Google Cloud Console and selected role Storage / Storage Admin (i.e. full control of GCS resources)....
Read more >Solved: Service account stopped working
Solved: I've been using a service account to load data into my gcp bucket. It was working fine for a year, and suddenly...
Read more >Troubleshoot Cloud Functions
If you attempt to invoke a function that does not exist, Cloud Functions responds with an HTTP/2 302 redirect which takes you to...
Read more >Service accounts overview | IAM Documentation
Conceptual and lifecycle information about IAM service accounts.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ah, I see that @jkwlui PR’s is for testing IAM so you need a different account, @laljikanjareeya is the the same for the refactor PR? If so, you can use the same account @jkwlui used in #1134 . I’ll add a TODO for myself to add that to an environment variable.
@amanda-tarafa Yes this is same for refactor PR and I will update the same thing in Storage Refactor Sample PR Once above PR gets merged.