-
-
Notifications
You must be signed in to change notification settings - Fork 132
Issues: Mongey/terraform-provider-kafka
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
forces replacement raised when topic name including character .
bug
#452
opened Aug 30, 2024 by
lzpsqzr
Is there any way to avoid touching
cleanup.policy
during UpdateTopic
?
#446
opened Aug 23, 2024 by
iamnotabout
Empty Summary: This is always a bug in the provider and should be reported to the provider developers.
bug
#442
opened Aug 12, 2024 by
lebohnes
MSK Serverless - The client is not authorized to access this topic
#434
opened Jul 28, 2024 by
Vijay-Kardile
Provider wants to replace existing kafka_acls when a new entry/ creating new resource is being added.
bug
#404
opened Apr 11, 2024 by
thennati
Using this provider with multiple AWS Kafka clusters in the same AWS account
#400
opened Mar 28, 2024 by
amplexus
Version 0.7.0 and 0.6.0 not working for kafka TLS brokers to create topics
#397
opened Mar 26, 2024 by
srikanth520
Version 0.7.0 does error on aim auth in comparison to 0.6.0
bug
#394
opened Mar 14, 2024 by
fritz-net
Terraform Plan takes a long time waiting for topics (intermittent)
#388
opened Feb 29, 2024 by
dslapelis
Enable the GSSAPI SASL mechanism for kerberos-based authentication
#376
opened Jan 30, 2024 by
hideyk
AWS MSK fresh cluster first apply fails because SASLS SCRAM secrets association is delayed
#364
opened Dec 12, 2023 by
eroznik
Timeout Exception with SASL SCRAM Authentication with AWS MSK
#342
opened Aug 29, 2023 by
sureshbandi
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.