Open Gowiem opened 6 months ago
Voting for Prioritization
Volunteering to Work on This Issue
Hey @Gowiem 👋 Thank you for taking the time to raise this! Can you verify whether the issue persists using Terraform as well? Debug logs are often useful as well, if you're able to provide them (redacted as needed).
@Gowiem Were you able to get a fix for this issue?
@elvis-mofor Nope. I believe this is still occurring and creating drift in our automation -- we just auto-apply over it. I don't have an easy way to confirm the same issue with Terraform. @oycyc might be able to provide some input as he's picked up my work on DMS.
Hey @Gowiem 👋 Thank you for taking the time to raise this! Can you verify whether the issue persists using Terraform as well? Debug logs are often useful as well, if you're able to provide them (redacted as needed).
@Gowiem Were you able to get a fix for this issue?
@justinretzolk @elvis-mofor This is still a persisting issue. Every time a plan / apply happens, these attributes changes in place even though there's nothing changing:
See these debug logs requested (with arn and other info removed): https://gist.github.com/oycyc/18daa8c0fbe280e191ef4585ed01e0e8
Terraform Core Version
tofu v1.6.1
AWS Provider Version
v5.38.0
Affected Resource(s)
aws_datasync_task
Expected Behavior
When no changes to configuration, no changes should show up in the plan.
Actual Behavior
On each plan of a simple
aws_datasync_task
resource, we're getting recurring "will be updated-in-place" changes on thetask_report_config.report_overrides
attribute block.Relevant Error/Panic Output Snippet
Terraform Configuration Files
Will post a child module that reproduces the issue soon.
Steps to Reproduce
aws_datasync_task
.Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None