-
Notifications
You must be signed in to change notification settings - Fork 248
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
Dynamic blocks do not fix the order in which listings are processed #1720
Comments
Hi @melumuccu, Thank you for reporting this issue. While reviewing the script we are suspecting that some changes were made outside of the terraform, Could you provide the following additional information to troubleshoot further on this issue.
|
Thanks for the reply.
Upon additional investigation, it appears that the order in which the arrays are processed in "for_each" in the dynamic block is undefined. Please see documents that follow. Sorry, The exact same dashboard had already been deleted, so I am attaching another dashboard with similar symptoms.
before "apply": https://gist.github.com/melumuccu/8f2e59b415753f5bb46e575827fb6ce7 I tried to get a before and after, but there is no difference...
I sent you an email. The title is this issue one. |
Hi @melumuccu |
@shiva-bandari This is the only thing I can come up with. |
Terraform Version
Affected Resource(s)
newrelic_one_dashboard
Terraform Configuration
Actual Behavior
After "apply", "change" was detected when "plan" was performed without modifying any source code.
Expected Behavior
No "change" was detected
Steps to Reproduce
logs
https://gist.github.com/melumuccu/2d9254ff3cf3d0135fef2b30cc6c4ac0
The text was updated successfully, but these errors were encountered: