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

Missing regions from costandusagereportservice > types.AWSRegion #3027

Open
2 of 3 tasks
ben-ganley opened this issue Mar 4, 2025 · 0 comments
Open
2 of 3 tasks

Missing regions from costandusagereportservice > types.AWSRegion #3027

ben-ganley opened this issue Mar 4, 2025 · 0 comments
Labels
service-api This issue is due to a problem in a service API, not the SDK implementation.

Comments

@ben-ganley
Copy link

ben-ganley commented Mar 4, 2025

Acknowledgements

Describe the bug

The github.com/aws/aws-sdk-go-v2/service/costandusagereportservice/types.AWSRegion enum is missing regions such as ap-southeast-5.

It is possible to create CUR with buckets in this region via the console but when attempted with Terraform that uses this enum as part of its validation, the process will fail due to the validation error.

Regression Issue

  • Select this option if this issue appears to be a regression.

Expected Behavior

The SDK should allow creation of this resource in ap-southeast-5

Current Behavior

Due to the missing region, Terraform's use of this enum causes the validation to fail.

Reproduction Steps

.

Possible Solution

Update the enum with all supported regions.

Additional Information/Context

No response

AWS Go SDK V2 Module Versions Used

.

Compiler and Version used

.

Operating System and version

.

@ben-ganley ben-ganley added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Mar 4, 2025
@lucix-aws lucix-aws added service-api This issue is due to a problem in a service API, not the SDK implementation. and removed needs-triage This issue or PR still needs to be triaged. bug This issue is a bug. labels Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service-api This issue is due to a problem in a service API, not the SDK implementation.
Projects
None yet
Development

No branches or pull requests

2 participants