-
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]: Importing an existing aws_cur_report_definition
appears to hang the terraform
client forever.
#36446
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Hey @spkane 👋 Thank you for taking the time to raise this! Are you able to provide a sample Terraform configuration that can be used to reproduce this? If you're able to, providing a more complete set of trace logs (redacted as needed) may help whoever winds up picking this up. |
@spkane Which AWS region are you applying the Terraform configuration on? I noticed in the When I tried to create the report using your provided configuration in Given the reason above, could you please try to manage your |
I will give this a try next week. However, the import still shouldn't be hanging the client. Ideally the logic would check the region and report a reasonable error back to the user if it is invalid for that resource type or at the very least timeout quickly. |
Agreed with the comment about additional safeguards on the hung call, but we want to make sure that you are at least unblocked first. I meant to take a crack at it later today, but might also need help from someone more experienced :) |
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.43.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.7
AWS Provider Version
5.40.0
Affected Resource(s)
aws_cur_report_definition
Expected Behavior
When trying to import an existing
aws_cur_report_definition
, I expect it to work or provide an actionable error.Actual Behavior
When running
terraform import aws_cur_report_definition.daily_athena DailyCostReport
theterraform
client appears to hang forever.Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
terraform import aws_cur_report_definition.daily_athena DailyCostReport
Debug Output
No response
Panic Output
No response
Important Factoids
terraform import
, I need to forcefully kill the process and then remove the state lock, as it doesn't appear to ever timeout and does not respond to [Control-C].References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: