Comments (4)
I have tried using terraform "0.12.1
and 0.11.7
with same outcome. It seems like conflict based in the kafka_topic.syslog.name
and kafka_acl.test.resource_name
which are both set to "syslog" and it works fine when these two are different.
from terraform-provider-kafka.
🤔 Very strange. I cannot reproduce this. Is the topic not in the state file?
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
+ kafka_topic.syslog
id: <computed>
config.%: "2"
config.retention.ms: "86400000"
config.segment.ms: "4000"
name: "syslog"
partitions: "4"
replication_factor: "1"
Plan: 1 to add, 0 to change, 0 to destroy.
Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.
Enter a value: yes
kafka_topic.syslog: Creating...
config.%: "" => "2"
config.retention.ms: "" => "86400000"
config.segment.ms: "" => "4000"
name: "" => "syslog"
partitions: "" => "4"
replication_factor: "" => "1"
kafka_topic.syslog: Creation complete after 2s (ID: syslog)
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
/private/tmp 3.69 conormongey@mbp
❯ terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.
kafka_topic.syslog: Refreshing state... (ID: syslog)
------------------------------------------------------------------------
No changes. Infrastructure is up-to-date.
This means that Terraform did not detect any differences between your
configuration and real physical resources that exist. As a result, no
actions need to be performed.
from terraform-provider-kafka.
Yes, here is the statefile
{
"version": 3,
"terraform_version": "0.11.7",
"serial": 1,
"lineage": "45c07565-034a-a601-5c15-da69f814504c",
"modules": [
{
"path": [
"root"
],
"outputs": {},
"resources": {
"kafka_acl.test": {
"type": "kafka_acl",
"depends_on": [],
"primary": {
"id": "User:Alice|*|Write|Deny|Topic|syslog|Literal",
"attributes": {
"acl_host": "*",
"acl_operation": "Write",
"acl_permission_type": "Deny",
"acl_principal": "User:Alice",
"id": "User:Alice|*|Write|Deny|Topic|syslog|Literal",
"resource_name": "syslog",
"resource_pattern_type_filter": "Literal",
"resource_type": "Topic"
},
"meta": {
"schema_version": "1"
},
"tainted": false
},
"deposed": [],
"provider": "provider.kafka"
},
"kafka_topic.syslog": {
"type": "kafka_topic",
"depends_on": [],
"primary": {
"id": "syslog",
"attributes": {
"config.%": "2",
"config.retention.ms": "86400000",
"config.segment.ms": "4000",
"id": "syslog",
"name": "syslog",
"partitions": "4",
"replication_factor": "1"
},
"meta": {},
"tainted": false
},
"deposed": [],
"provider": "provider.kafka"
}
},
"depends_on": []
}
]
}
from terraform-provider-kafka.
Having the same issue @tundeaoni where you able to work around this?
from terraform-provider-kafka.
Related Issues (20)
- Import of Scram Credential Resource
- password changes in scram credentials not detected HOT 1
- AWS MSK fresh cluster first apply fails because SASLS SCRAM secrets association is delayed
- Enable the GSSAPI SASL mechanism for kerberos-based authentication
- Add support for oauthbearer as the sasl mechanism HOT 6
- Unable to use aws-iam with Apache Kafka version 2.5.1 HOT 1
- Provider not working since version 0.6 HOT 22
- Terraform Plan takes a long time waiting for topics (intermittent)
- Ho do I use a PKCS12 keystore for MSK authentication?
- Version 0.7.0 does error on aim auth in comparison to 0.6.0 HOT 6
- Version 0.7.0 and 0.6.0 not working for kafka TLS brokers to create topics
- Version 0.7.0 and 0.6.0 not working for kafka TLS brokers to create topics
- Using this provider with multiple AWS Kafka clusters in the same AWS account HOT 1
- Provider wants to replace existing kafka_acls when a new entry/ creating new resource is being added. HOT 7
- `terraform plan` returns unexpected diff if brokers have cluster-wide default config HOT 1
- Overrides for Topic Placement Policy HOT 1
- Kafka Compatibility Query HOT 2
- Kafka Broker Issue HOT 1
- Provider Cannot Assume Role From EKS HOT 2
- Empty Summary: This is always a bug in the provider and should be reported to the provider developers
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from terraform-provider-kafka.