hashicorp / terraform-provider-aws

The AWS Provider enables Terraform to manage AWS resources.
https://registry.terraform.io/providers/hashicorp/aws
Mozilla Public License 2.0
9.75k stars 9.1k forks source link

[Tech Debt]: Serialize `aws_finspace_kx_*` acceptance tests #32646

Closed jar-b closed 1 year ago

jar-b commented 1 year ago

Description

The FinSpace managed kdb resource acceptance tests all require a kdb environment to execute. The default quota for Total kdb environments is 1, so to avoid LimitExceeded exceptions these tests should be serialized.

Example parallel test failure:

=== RUN   TestAccFinSpaceKxEnvironment_description
=== PAUSE TestAccFinSpaceKxEnvironment_description
=== CONT  TestAccFinSpaceKxEnvironment_description
    kx_environment_test.go:141: Step 1/2 error: Error running apply: exit status 1
        Error: creating Amazon FinSpace Kx Environment (tf-acc-test-736091273136364188): operation error finspace: CreateKxEnvironment, exceeded maximum number of attempts, 25, https response error StatusCode: 400, RequestID: 0a261b33-8fef-4655-aa52-85254aee3aef, LimitExceededException: Create environment failed due to capacity limit reached, environment name: tf-acc-test-736091273136364188
          with aws_finspace_kx_environment.test,
          on terraform_plugin_test.tf line 6, in resource "aws_finspace_kx_environment" "test":
           6: resource "aws_finspace_kx_environment" "test" {
--- FAIL: TestAccFinSpaceKxEnvironment_description (614.08s)
FAIL

References

Would you like to implement a fix?

None

github-actions[bot] commented 1 year ago

Community Note

Voting for Prioritization

Volunteering to Work on This Issue

github-actions[bot] commented 1 year ago

This functionality has been released in v5.11.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!

github-actions[bot] commented 1 year ago

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.