Why is my terraform init automation script failing?
I am a Terraform (provider) newbee and I try to create an out of the box working script that runs terraform init and does all the preparation that is needed to make that working. For example, registry lookups should be avoided at all times as the Terraform provider to use is just a local binary.
Why does the folder check in Terraform contradict my Python output?
I am a newbee when it comes to Terraform providers which may explain why I have the following problem on my Ubuntu 24.04 V. First, here is the main.tf file:
Why does the folder check in Terraform contradict my Python output?
I am a newbee when it comes to Terraform providers which may explain why I have the following problem on my Ubuntu 24.04 V. First, here is the main.tf file:
Why does the folder check in Terraform contradict my Python output?
I am a newbee when it comes to Terraform providers which may explain why I have the following problem on my Ubuntu 24.04 V. First, here is the main.tf file:
Terraform Storage Bucket Encryption is not working
I have a terraform script that creates a storage bucket and adds encryption to it. I already have a KMS key rings and the key created. I also have a service account with the following roles
“CLOUD KMS ADMIN” “Cloud KMS CryptoKey Encrypter/Decrypter”
Failed to read a output variable returned by a terraform module when upgraded terraform-provider-google from version v4.85.0 to 5.x.x
I have a module that return a variable named “spot_account_id” and we use this variable to create other terraform resource further.
Terraform plan is working fine untill I’m not upgrading google provider version.
As soon I upgrade google provider version from v4.85.0 to v5.39.0 and perform terraform plan, I’m unable to get “spot_account_id” from module in return.
Terraform dynamic block for GCP firestore
I’m trying to create a module for GCP firestore that creates a single database which can create multiple indexes with multiple fields but am having some trouble.
Terraform module override new attributes
In our existing infra, we calling version 7.4.0 of the following module in our own module.