-
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
[Bug]: Unable to update MSK cluster policy after enabling multi-VPC connectivity #35538
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Potentially related #34419 (see this comment specifically) |
Is there any update on this? I raised the same issue sometime back and they rolled out a fix. but, looks like it's back again. How can this happen? |
@ewbankkit Sometime back you fixed this same issue with #33107. But, It looks to have come back. I even used same provider version which originally worked (
Here is the output from the TF Debug log enabled,
Are you able to see if you can help with this? Thank you in advance. |
Here is another thing I discovered. This error only shows up when |
Terraform Core Version
1.7.0
AWS Provider Version
5.34.0
Affected Resource(s)
aws_msk_cluster_policy
Expected Behavior
After enabling multi-VPC connectivity for MSK cluster it should be possible to update
aws_msk_cluster_policy
.Actual Behavior
When I create a MSK cluster policy using
aws_msk_cluster_policy
I am receiving:during
terraform plan
it looks liketerraform
is not aware of existingaws_msk_cluster_policy
- it does not modify resource but adds new one.Relevant Error/Panic Output Snippet
Basically, terraform is not aware that `aws_msk_cluster_policy` exist and is not pulling the current policy version prior to being updated.
Terraform Configuration Files
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
This issue looks similar to this one: #33107
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: