Repository navigation
Enable CI testing of 'requester_pays' / 'user_project' feature #4126
Description
Update .circleci/config.yml to set the GOOGLE_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.
Activity
dhermes commentedon Oct 5, 2017
@tseaver We should set env. variables in the project settings, not in
.circleci/config.ymltseaver commentedon Oct 5, 2017
Ah, thanks for clarification.
tseaver commentedon Oct 9, 2017
@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.
tseaver commentedon Jan 8, 2018
#4125 is now closed: the tests run cleanly for me locally, when I set
GOOGLE_CLOUD_TESTS_USER_PROJECTto point at my "private" project (running with the "normal" CI account as the main one).tseaver commentedon Jan 8, 2018
@lukesneeringer I think we're ready to configure the "user project" to be used as the
user_projectfor those tests under CI. I can't recall which one we agreed to use, though: if you'll follow up here to let me know, I will create a PR updating the CircleCI config to set it.Note that the service account as which we normally run will need to be configured with the 'project.editor' role on the new one.
tseaver commentedon Jul 20, 2018
@theacodes, @JustinBeckwith can one of your set up a second project with the
project.editorrole assigned to our CI project? We will then need to set that project in the CI environment asGOOGLE_CLOUD_TESTS_USER_PROJECT, at which point those system tests will no longer be skipped.crwilcox commentedon Oct 18, 2019
@tseaver is this still needed?
busunkim96 commentedon Jan 29, 2020
Closing as this seems obsolete.