Priit Pihus

> I understand you can't use a for_each expression with this resource because it will remain only the last iteration of the loop? Yes, and you also can't use this...

Thank you @jandillenkofer. I vote going with the same resource and `secret_arn_list`. While theoretically it is indeed a breaking change, I do not see it being a problem in any...

What would be the difference between having `aws_msk_single_scram_secret_association` vs using the existing resource and putting only one arn in `secret_arn_list` though?

From @jandillenkofer's initial explanation I understood that it would be possible to keep only one resource, but still maintain each scram association separately. They initially suggested it can be done...

I understand, but this violates the very key principles of **idempotency** and makes a great risk for configuration drift because of the "_last writer wins_" pattern. Are there any other...

Can you elaborate why would this be better than just having one item in the `secret_arn_list`? Also a question about a theoretical secnario. What if you initially have: ```hcl resource...