Open lebohnes opened 2 weeks ago
Voting for Prioritization
Volunteering to Work on This Issue
Hey @lebohnes 👋 Thank you for taking the time to raise this! When you run a terraform plan
, are you seeing any changes to the reported value for sasl_scram_512_auth
? If you're able to supply debug logs (redacted as needed), it may be helpful to whoever picks this up.
@justinretzolk No, i don't see any changes for sasl_scram_512_auth
.. here is the terraform plan output. I hope it helps:
# module.msk-consumer-pipe["resource_name"].module.msk_consumer.aws_pipes_pipe.msk_consumer will be updated in-place
~ resource "aws_pipes_pipe" "msk_consumer" {
id = "resource_name"
name = "resource_name"
tags = {}
# (9 unchanged attributes hidden)
~ source_parameters {
~ filter_criteria {
~ filter {
~ pattern = jsonencode(
~ {
~ value = {
+ clusterTime = [
+ {
+ numeric = [
+ ">=",
+ 1724768012,
]
},
]
- data = {
- operationType = [
- "update",
]
}
}
}
)
}
- filter {
- pattern = jsonencode(
{
- value = {
- clusterTime = [
- {
- numeric = [
- ">=",
- 1724768012,
]
},
]
}
}
) -> null
}
}
# (1 unchanged block hidden)
}
# (2 unchanged blocks hidden)
}
Terraform Core Version
1.9.3
AWS Provider Version
5.62.0
Affected Resource(s)
Expected Behavior
The resource should update properly, the
data.aws_secretsmanager_secret.msk_cluster_credentials.arn
is unchanged and should not result in an errorActual Behavior
Terraform fails to update the resource with an operation error.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
Create the resource => Update the resource e.g. by updating a filter or an iam role
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None