-
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]: Order lost in aws_quicksight_data_set
causing endless plan updates due to ordering of principals in permissions
block
#32645
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
terraform-provider-aws/internal/service/quicksight/data_set.go Lines 201 to 205 in 22f8b22
|
Thank you for point this out @jar-b. |
This functionality has been released in v5.13.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform Core Version
1.5.3
AWS Provider Version
5.8.0
Affected Resource(s)
The
permissions
block inaws_quicksight_data_set
resourceExpected Behavior
When running multiple plans without changes to the Terraform configuration file, Terraform should detect no changes
Actual Behavior
When running multiple plans without changes to the Terraform configuration file, changes are detected on every plan due to reordering of the principals
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
terraform apply
terraform plan
Notice there's significance to the usernames.
The usernames I'm using in the
users
list are returned in reversed order interraform plan
(step 2 above), and this is what's causing the drift.Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
#22274
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: