-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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]: Regression in 5.39.0 #36056
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Thank you for raising this. This is fixed by #36054 and will be available in v5.39.1. |
This functionality has been released in v5.39.1 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.7.1
AWS Provider Version
5.39.0
Affected Resource(s)
EC2 instance, specifically reading ebs tags_all
Expected Behavior
Reads happen properly
Actual Behavior
╷
│ Error: reading EC2 Instance (i-123456789): reading EC2 Instance (i-123456789): Invalid address to set: []string{"ebs_block_device", "0", "tags_all"}
│
│ with module.environment_stg.module.ebs_volumes["ec2"].data.aws_instance.attachment_target,
│ on .terraform/modules/environment_stg.ebs_volumes/main.tf line 1, in data "aws_instance" "attachment_target":
│ 1: data "aws_instance" "attachment_target" {
│
╵
Relevant Error/Panic Output Snippet
Terraform Configuration Files
There is a lot of code associated with this and very specific to my use case which would be a great deal of work to anonymize. In any case since it works with 5.38.0 and not with 5.39.0 it does not seem entirely necessary.
Steps to Reproduce
Running this plan with 5.39.0 results in the above errors, 5.38.0 plans and applies properly.
Debug Output
No response
Panic Output
No response
Important Factoids
Seems to be a duplicate of this bug #17125
References
My best guess is one of these commits from @YakDriver who also fixed the previous bug (possible duplicate/regression) #17125
c9769c9
4c3e2c5
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: