-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
New Resource: aws_msk_configuration #8740
Conversation
Reference: #8736 Output from acceptance testing: ``` --- PASS: TestAccAWSMskConfiguration_KafkaVersions (14.14s) --- PASS: TestAccAWSMskConfiguration_Description (19.35s) --- PASS: TestAccAWSMskConfiguration_basic (27.64s) --- PASS: TestAccAWSMskConfiguration_ServerProperties (29.51s) ```
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One slight issue with the resource documentation, but otherwise good to go +1
|
||
~> **NOTE:** The API does not support deleting MSK configurations. Removing this Terraform resource will only remove the Terraform state for it. | ||
|
||
~> **NOTE:** This AWS service is in Preview and may change before General Availability release. Backwards compatibility is not guaranteed between Terraform AWS Provider releases. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯
Co-Authored-By: Wilken Rivera <dev@wilkenrivera.com>
This has been released in version 2.12.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
Hi Guys, I'm struggling here , how do I link an aws_msk_configuration to an aws_msk_cluster so that the cluster allows topics to be deleted ? |
@paulca99 this requires the resource "aws_msk_configuration" "example" {
kafka_versions = ["1.1.1"]
name = "example"
server_properties = <<PROPERTIES
delete.topic.enable = true
PROPERTIES
}
resource "aws_msk_cluster" "example" {
cluster_name = "example"
kafka_version = "1.1.1"
number_of_broker_nodes = 3
broker_node_group_info {
client_subnets = ["${aws_subnet.example1.id}", "${aws_subnet.example2.id}", "${aws_subnet.example3.id}"]
ebs_volume_size = 10
instance_type = "kafka.m5.large"
security_groups = ["${aws_security_group.example.id}"]
}
configuration_info {
arn = "${aws_msk_configuration.example.arn}"
revision = "${aws_msk_configuration.example.latest_revision}"
}
} |
Thanks @bflad |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Closes #8736
Release note for CHANGELOG:
Output from acceptance testing: