Lines Matching +full:gcp +full:- +full:service +full:- +full:account

4 same GCP project resources, required resources not existing on the GCP project, quota limits being
6 service account impersonation requirements.
9 and on-prem resources to be defined in configuration files to be versioned, reused, and shared. By
10 using Terraform to provision our GCP projects prior to running integration tests we:
13 * Prevent conflicts between concurrent integration test invocations using the same GCP project by
15 * Provide a managed lifecycle including the ability to destroy short-lived testing environments,
18 # Running `google-cloud-java` Integration Tests
20 When you need to troubleshoot integration tests in the google-cloud-java repository, follow one of
21 the supported workflows below to provision a GCP project with the required configuration.
30 …[About Cloud Billing accounts](https://cloud.google.com/billing/docs/how-to/manage-billing-account)
32 …ting and managing Folders](https://cloud.google.com/resource-manager/docs/creating-managing-folder…
36 export GOOGLE_CLOUD_BILLING_ACCOUNT="000000-000000-000000"
37 export GOOGLE_CLOUD_PROJECT_PREFIX="my-project"
43 optionally creates a GCP project, and then sets up the
44 [application-default credentials](https://cloud.google.com/docs/authentication/application-default-…
47 A service account will be created, assigned `roles/owner`[^1], and used for all client library
48 integration tests. Your user credentials must have permission in the designated GCP project to
49 self-assign `roles/iam.serviceAccountTokenCreator` to impersonate the service account.
52 [not recommended in production environments](https://cloud.google.com/iam/docs/understanding-roles#…
55 ### Workflow: Set up a GCP Project for **One or More** Client Libraries, then Test
63     * `./.cloud/setup.sh java-accessapproval`
64     * `./.cloud/setup.sh java-asset,java-compute,java-container`
72     * `./.cloud/verify.sh java-accessapproval`
73     * `./.cloud/verify.sh java-asset,java-compute,java-container`
76 libraries. In this workflow, the GCP project will only have been configured the project for a subset
77 of client libraries, this command is unlikely to succeed unless the GCP project has been previously
81 ### Workflow: Set up a GCP Project for **All** Client Libraries, then Test
88    root module, and the GCP project will be prepared to test all client libraries.
101     * `./.cloud/verify.sh java-accessapproval`
102     * `./.cloud/verify.sh java-asset,java-compute,java-container`
115 * `./.cloud/test.sh java-accessapproval`
116 * `./.cloud/test.sh java-asset,java-compute,java-container`
118 ### Workflow: Clean up GCP Project of Test Resources
120 To clean-up (or “destroy”) all provisioned resources under Terraform’s management,
129 Terraform will automatically manage the resources for a GCP project when regenerating the root
131 use-case.
136 $ ./.cloud/setup.sh java-bigqueryconnection
137 # Terraform provisions the project for java-bigqueryconnection's requirements.
139 $ ./.cloud/setup.sh java-accessapproval
140 # Terraform simultaneously destroys java-bigqueryconnection's resources that
141 # are no longer being used, and provisions the project for java-accessapproval's
146 $ ./.cloud/setup.sh java-accessapproval,java-texttospeech
147 # Terraform maintains the java-accessapproval resources while also provisioning
148 # the project for java-texttospeech's requirements.