You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
╷
│ Error: googleapi: Error 403: Your application has authenticated using end user credentials from the Google Cloud SDK or Google Cloud Shell which are not supported by the admin.googleapis.com. We recommend configuring the billing/quota_project setting in gcloud or using a service account through the auth/impersonate_service_account setting. For more information about service accounts and how to use them in your application, see https://cloud.google.com/docs/authentication/. If you are getting this error with curl or similar tools, you may need to specify 'X-Goog-User-Project' HTTP header for quota and billing purposes. For more information regarding 'X-Goog-User-Project' header, please check https://cloud.google.com/apis/docs/system-parameters., accessNotConfigured
│
│
╵
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
I believe there are two separate ways this issue could be solved: one, the provider could respect the impersonated_user_email setting when used with application default credentials (currently it only does when an explicit JWT is passed, see [1]); or two, the provider could implement a billing_project setting (similar to the google provider: https://registry.terraform.io/providers/hashicorp/google/latest/docs/guides/provider_reference#billing_project).
Terraform Version
Affected Resource(s)
googleworkspace_group
Terraform Configuration Files
Debug Output
N/A
Panic Output
N/A
Expected Behavior
Running
terraform import
works.Actual Behavior
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
gcloud auth application-default login --scopes "https://www.googleapis.com/auth/cloud-platform,https://www.googleapis.com/auth/admin.directory.group.readonly"
terraform import
Important Factoids
I believe there are two separate ways this issue could be solved: one, the provider could respect the
impersonated_user_email
setting when used with application default credentials (currently it only does when an explicit JWT is passed, see [1]); or two, the provider could implement abilling_project
setting (similar to thegoogle
provider: https://registry.terraform.io/providers/hashicorp/google/latest/docs/guides/provider_reference#billing_project).[1]
terraform-provider-googleworkspace/internal/provider/provider_config.go
Lines 39 to 64 in 82ecae6
References
None that I could find.
The text was updated successfully, but these errors were encountered: