Background:
Currently I have an existing GCP VPC-SC Service Perimeter which was created and is managed using Terraform via a Cloud Build Pipeline. In it’s current state, the Terraform Provider version being defined is 4.28, which you can see below.

I am using terraform through Gitlab CI/CD to create resources on Google Cloud. To achieve this I have tried two different approaches. (i) Base64 Encoded service account key file locally on my laptop with passphrase and upload that file to repo and then added decoding steps in my .gitlab-ci.yml file in terraform stage. Also, added a path to this decoded file into providers.tf – This approach works without any issues (ii) Base64 Encoded service account key file and added encoded contents as a value to a gitlab CI/CD variable and tried to decode that variable in .gitlab-ci.yml file which runs into error “Error: the string provided in credentials is neither valid json nor a valid file path”

I am trying to supply the GCP application credentials to terraform via the HashiCorp vault. I have managed to do it by first executing gcloud auth application-default login, but I would like to automate the process. Details below.

I should have all permissions including compute.addresses.create, why can I not configure a static IP address with Terraform? The configuration I’m adding is as follows:

Using Terraform in my local terminal, I’ve been trying to disable the Disable Service Account Key Creation policy for a specific project and stop it from inheriting the policy from the parent organization.

I want to import terraform of GCP’s OAuth 2.0 client. However, I don’t know terraform’s resource name of OAuth client.

I want to import terraform of GCP’s OAuth 2.0 client. However, I don’t know terraform’s resource name of OAuth client.