Skip to content
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

storage: re-write Bucket system test to not require custom IAM permissions #2224

Closed
stephenplusplus opened this issue Apr 14, 2017 · 3 comments
Assignees
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release.

Comments

@stephenplusplus
Copy link
Contributor

stephenplusplus commented Apr 14, 2017

@lukesneeringer can you bump the IAM permissions, granting a Storage owner role https://console.cloud.google.com/iam-admin/iam/project?project=long-door-651 for those service accounts? Honestly not sure which one we're using with Circle and AppVeyor, probably one of the Google APIs service accounts.

Error logging:

  • "Caller does not have storage.buckets.update access to bucket gcloud-test-89de9880-51d5-11e7-83ed-a1b6d76c8415."
  • "Caller does not have storage.objects.create access to bucket gcloud-test-fa0d5b40-51d6-11e7-adb9-95d6981c1286."
  • "Caller does not have storage.objects.delete access to bucket gcloud-test-eb034cd0-51d7-11e7-b891-8515c90cd604."
@stephenplusplus
Copy link
Contributor Author

@lukesneeringer lukesneeringer added the priority: p2 Moderately-important priority. Fix may not be included in next release. label Apr 19, 2017
@stephenplusplus stephenplusplus changed the title System Test Service Account IAM permissions storage: re-write Bucket system test to not require custom IAM permissions Jun 12, 2017
@stephenplusplus
Copy link
Contributor Author

@swcloud - would you please look into this? Our system tests are also unable to delete the files in the buckets we create during the tests.

@swcloud
Copy link
Contributor

swcloud commented Jun 23, 2017

Please try again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release.
Projects
None yet
Development

No branches or pull requests

3 participants