-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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]: Unexpected id from data.aws_efs_access_point when upgrading yo 5.58.0 #38355
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
v5.57.0
v5.58.0terraform-provider-aws/internal/service/efs/access_point_data_source.go Lines 116 to 117 in 5b5e529
|
Warning This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
This functionality has been released in v5.59.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.9.2
AWS Provider Version
5.58.0
Affected Resource(s)
data aws_efs_access_point
Expected Behavior
expected
data.aws_efs_access_point.efs_access_point.id
to return a file system access point id, e.g.Actual Behavior
data.aws_efs_access_point.efs_access_point.id
returns the file system id, e.g.Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
I don't know how to do this, it is part of a much bigger pipeline and I don't have my own AWS access
Debug Output
No response
Panic Output
No response
Important Factoids
Happened on upgrade from 5.57.0 to 5.58.0
References
No response
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: