-
Notifications
You must be signed in to change notification settings - Fork 0
Odb aws 5 #6
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
…-data_source-add_load_balancer [Enhancement]d/aws_ecs_service: Support `load_balancer` attribute
…roup-idc resource/aws_athena_workgroup: Add identity_center_configuration block
…support_volume_initilization_rate [Enhancement] aws_ebs_volume: Support `volume_initialization_rate` argument
…dates `aws-sdk-go-v2` updates (Release 2025-07-28)
…h a single newline character'.
r/aws_ssm_parameter: update `version` attr when `description` arg changes
…key_registration New resource: `aws_quicksight_key_registration`
``` 2025/07/29 17:03:08 - aws_fsx_s3_access_point_attachment: listing "aws_fsx_s3_access_point_attachment" (us-west-1): operation error FSx: DescribeS3AccessPointAttachments, https response error StatusCode: 400, RequestID: 14c7a9f4-d964-4736-a908-b93366371f56, UnsupportedOperation: This operation is unsupported. ```
``` 2025/07/29 17:03:08 - aws_prometheus_scraper: listing "aws_prometheus_scraper" (us-west-1): operation error amp: ListScrapers, exceeded maximum number of attempts, 5, https response error StatusCode: 500, RequestID: 7fcd350e-6973-48a1-8c10-9d3458fc856c, api error InternalServerErrorException: Internal server error ```
internal/sweep: Additional skippable errors
…leet-add_instance_type [Enhancement] aws_codebuild_fleet: Support custom instance type in the fleet
|
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 with Hashicorp repo to resolve merge conflict