-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terraform keeps forcing new resource on unchanged cluster #26
Comments
@nbommu1 What version of the provider are you using? can you try |
I was trying with ver 0.0.3 downloaded from below url. https://github.com/Mongey/terraform-provider-confluentcloud/releases/tag/v0.0.3 |
I rebuilt the module from the source, now it works.
|
when I build that from source still I have to define this in my terraform, is this right way to do this? |
another error when I create cluster with error: Error applying plan: 1 error occurred: |
intersting, if build the module from the source it works fine, here is my terraform. resource "confluentcloud_kafka_cluster" "test" {
name = "test"
service_provider = "aws"
region = "us-east-1"
availability = "HIGH"
environment_id = confluentcloud_environment.environment.id
network_egress = 100
network_ingress = 100
storage = 5000
deployment = { "sku": "STANDARD" }
}
|
@nbommu1 - I have no issue with version |
Hi,
I have an issue on cluster in confluent cloud, it keeps forcing new resource on unchanged cluster.
`-/+ confluentcloud_kafka_cluster.test (new resource required)
id: "lkc-nkqz6" => (forces new resource)
availability: "LOW" => "LOW"
bootstrap_servers: "SASL_SSL://pkc-4nym6.us-east-1.aws.confluent.cloud:9092" =>
deployment.%: "1" => "0" (forces new resource)
deployment.sku: "BASIC" => "" (forces new resource)
environment_id: "env-7qnnp" => "env-7qnnp"
name: "provider-test" => "provider-test"
network_egress: "100" => "100"
network_ingress: "100" => "100"
region: "us-east-1" => "us-east-1"
service_provider: "aws" => "aws"
storage: "5000" => "5000"
`
what are default values to set deployment?
thanks
Niranjan
The text was updated successfully, but these errors were encountered: