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
Trying to create a cluster using Vault, setting only the required input variables, fails with "read_capacity can not be set when billing_mode is "PAY_PER_REQUEST"
Steps to reproduce the behavior
Creating new git repos for terraform and cluster, run terraform init, then terraform plan
Expected behavior
It installs
Actual behavior
Fails with
read_capacity can not be set when billing_mode is "PAY_PER_REQUEST"
write_capacity can not be set when billing_mode is "PAY_PER_REQUEST"
Terraform version
The output of terraform version is:
Terraform v1.0.7
on darwin_amd64
+ provider registry.terraform.io/hashicorp/aws v3.73.0
+ provider registry.terraform.io/hashicorp/cloudinit v2.2.0
+ provider registry.terraform.io/hashicorp/helm v2.4.1
+ provider registry.terraform.io/hashicorp/kubernetes v2.7.1
+ provider registry.terraform.io/hashicorp/local v2.1.0
+ provider registry.terraform.io/hashicorp/null v3.1.0
+ provider registry.terraform.io/hashicorp/random v3.1.0
+ provider registry.terraform.io/hashicorp/template v2.2.0
+ provider registry.terraform.io/terraform-aws-modules/http v2.4.1
Your version of Terraform is out of date! The latest version
is 1.1.4. You can update by downloading from https://www.terraform.io/downloads.html```
I could fix the problem by adding a versions.tf file in my repo, and setting
Summary
Trying to create a cluster using Vault, setting only the required input variables, fails with
"read_capacity can not be set when billing_mode is "PAY_PER_REQUEST"
Steps to reproduce the behavior
Creating new git repos for terraform and cluster, run terraform init, then terraform plan
Expected behavior
It installs
Actual behavior
Fails with
Terraform version
The output of
terraform version
is:I could fix the problem by adding a versions.tf file in my repo, and setting
The text was updated successfully, but these errors were encountered: