Closed ascpikmin closed 5 months ago
I think we can support that here if you would like to open a PR for it
@bryantbiggs I am interested in resolving this issue as well! I have opened a pull-request which I believe solves the issue. Please could you review this?
All the best,
Gregg
This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days
Hi @bryantbiggs is there any chance you can take a look at https://github.com/terraform-aws-modules/terraform-aws-msk-kafka-cluster/pull/17? Cheers
@bryantbiggs you might have a closer look at already opened and closed PRs. This issue may have been long fixed.
This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days
This issue was automatically closed because of stale in 10 days
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Description
When I try to update the Kafka version on the module, the
aws_msk_configuration
resource fails because this version change requires its destruction, and this is not possible because it is being used by the msk cluster.If your request is for a new feature, please use the
Feature request
template.⚠️ Note
Before you submit an issue, please perform the following first:
.terraform
directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!):rm -rf .terraform/
terraform init
Versions
Module version [Required]: 2.3.0
Terraform version: 1.6.3
Provider version(s): provider registry.terraform.io/hashicorp/aws v5.26.0 provider registry.terraform.io/hashicorp/random v3.5.1
Reproduction Code [Required]
Steps to reproduce the behavior:
Expected behavior
That the new
aws_msk_configuration
resource be created before deleting the old oneActual behavior
The previous
aws_msk_configuration
resource tries to be deleted before creating the new one and it cannot because it is being used by the clusterTerminal Output Screenshot(s)
Additional context
If you set the
configuration_name
parameter to a dynamic name and manually change theaws_msk_configuration
resource and add alifecycle {create_before_destroy = true}
, it updates successfully, so I don't know if this would be the solution.