-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Enable CI testing of 'requester_pays' / 'user_project' feature #4126
Comments
@tseaver We should set env. variables in the project settings, not in |
Ah, thanks for clarification. |
@lukesneeringer In order to start using the 'gcloud-....-whitelist-not-really' project for CI, we need to either: a> grant our existing CI system account the appropriate permissions on the new project; or b) create a new system account with appropriate permissions, and then re-do our system tests so that they use those creds. I would prefer a), as it would let the tests as-written just work. |
#4125 is now closed: the tests run cleanly for me locally, when I set |
@lukesneeringer I think we're ready to configure the "user project" to be used as the Note that the service account as which we normally run will need to be configured with the 'project.editor' role on the new one. |
@theacodes, @JustinBeckwith can one of your set up a second project with the |
@tseaver is this still needed? |
Closing as this seems obsolete. |
Update
.circleci/config.yml
to set theGOOGLE_CLOUD_TESTS_USER_PROJECT
environment variable to point at a different project than the default one supplied by our credentials.Until then, the system tests for
user_project
/requester_pays
will be skipped.Note that #4125 will cause system test failures, so we should defer this task until the back-end team releases their fix.
The text was updated successfully, but these errors were encountered: