-
Notifications
You must be signed in to change notification settings - Fork 0
Sync with upstream 1 #19
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
Conversation
Fix for error message: """ error creating Service Catalog Portfolio Share: InvalidStateException: Cannot process more than one portfolio share action at the same time. Try again later. """
AWS will let the portfolio share create succeed, then register a ThrottlingException in the share status if it happened too soon. Rather than trying to detect this and recreate the share, just sleep after each share create to not do too many at a time.
…sist [bug] Fix inconsistent final plan for tgw association/propagation
The channel ID has updated following migration to IBM slack.
…metric_alarm-add_example_metrics_insights [Docs] aws_cloudwatch_metric_alarm: Add an example and description about Metrics Insights query
chore: update release notification channel
F aws_rds_global_cluster data source
…ation Public documentation fix for odb
…ashicorp#44638) * Add pro roles * Update documentation * Add changelog
Update EBS gp3 throughput maximum from 1000 to 2000 MiB/s
Community GuidelinesThis comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀 Voting for Prioritization
Pull Request Authors
|
|
Warning This Issue has been closed, meaning that any additional comments are much easier for the maintainers to miss. 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. |
sync the fork with HashiCorp