-
Notifications
You must be signed in to change notification settings - Fork 9k
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]: idle_disconnect_timeout_in_seconds parameter in aws_appstream_fleet ressource doesn't support a value greater than 3600 #34453
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Can I work on this one @justinretzolk? |
I see a discrepancy between the maximum time in the AWS console and the AWS API documentation.
Can anyone clarify the correct timeout period? |
AWS support informed me that the API documentation will be updated to reflect this change. |
Any update on this pls ? |
This functionality has been released in v5.32.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.25.0
Affected Resource(s)
aws_appstream_fleet
Expected Behavior
idle_disconnect_timeout_in_seconds parameter set to a value greater than 3600 seconds, for example 7200
Actual Behavior
idle_disconnect_timeout_in_seconds parameter cannot be set to a value greater than 3600 seconds.
Relevant Error/Panic Output Snippet
Error: expected idle_disconnect_timeout_in_seconds to be in the range (60 - 3600), got 7200
Terraform Configuration Files
Steps to Reproduce
Create an appstream fleet with idle_disconnect_timeout_in_seconds parameter set to a value greater than 3600.
Debug Output
No response
Panic Output
Error: expected idle_disconnect_timeout_in_seconds to be in the range (60 - 3600), got 7200
Important Factoids
idle_disconnect_timeout_in_seconds parameter can be set to a value greater than 3600 through aws cli :
aws appstream describe-fleets --name xxxxx --query 'Fleets[*].IdleDisconnectTimeoutInSeconds' [ 7200 ]
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: