Skip to content
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

Closed
got2be71 opened this issue Nov 17, 2023 · 7 comments · Fixed by #35173
Labels
bug Addresses a defect in current functionality. good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. service/appstream Issues and PRs that pertain to the appstream service.
Milestone

Comments

@got2be71
Copy link

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

resource "aws_appstream_fleet" "this" {
  [...]
  idle_disconnect_timeout_in_seconds = 7200
  [...]
}

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 update-fleet --name xxxxx --idle-disconnect-timeout-in-seconds 7200
aws appstream describe-fleets --name xxxxx  --query 'Fleets[*].IdleDisconnectTimeoutInSeconds'
[
    7200
]

References

No response

Would you like to implement a fix?

None

@got2be71 got2be71 added the bug Addresses a defect in current functionality. label Nov 17, 2023
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added the service/appstream Issues and PRs that pertain to the appstream service. label Nov 17, 2023
@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label Nov 17, 2023
@justinretzolk justinretzolk added good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. and removed needs-triage Waiting for first response or review from a maintainer. labels Nov 17, 2023
@Deathfireofdoom
Copy link

Can I work on this one @justinretzolk?

@jrang188
Copy link

I see a discrepancy between the maximum time in the AWS console and the AWS API documentation.

  • In the AWS console, the maximum time is 600 minutes (36000 seconds)
    image
  • The API documentation shows the current 60 to 3600 seconds.
    image
    IdleDisconnectTimeoutInSeconds

Can anyone clarify the correct timeout period?

@got2be71
Copy link
Author

AWS support informed me that the API documentation will be updated to reflect this change.

@got2be71
Copy link
Author

Any update on this pls ?

Copy link

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!

Copy link

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. service/appstream Issues and PRs that pertain to the appstream service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants