-
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
r/aws_appstream_fleet: Update max_user_duration_in_seconds
to 432000
#32933
r/aws_appstream_fleet: Update max_user_duration_in_seconds
to 432000
#32933
Conversation
Community NoteVoting for Prioritization
For Submitters
|
max_duration_in_seconds
to 432000
max_user_duration_in_seconds
to 432000
Changes all look good - working on fixing the acceptance tests. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🎉
On second thought, will open a separate PR with acceptance test fixes for several AppStream resources.
This functionality has been released in v5.12.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 pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
This PR updates the
aws_appstream_fleet
resource'smax_user_duration_in_seconds
argument validation to allow the use of up to432000
, as per the AWS API documentation.Relations
Closes #32874
References
Output from Acceptance Testing
I don't have the necessary permissions to successfully run the tests in the accounts I have access to, unfortunately.