tests/resource/workspaces_directory: Fix hardcoded region

[YakDriver]

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Relates #12995 Phase 2

Release note for CHANGELOG:

NONE

Acceptance Tests in GovCloud

--- SKIP: TestAccAwsWorkspacesDirectory_basic (2.36s)

Acceptance Tests in us-west-2

--- PASS: TestAccAwsWorkspacesDirectory_basic (615.53s)

Acceptance Tests in us-east-1

--- PASS: TestAccAwsWorkspacesDirectory_basic (911.57s)

[bflad]

In this case, I think lint ignoring is fine and we should prefer to keep the region name in the configuration for clarity, since it looks like the local is written to be expanded in the future. 👍 (I have not done any research to see if there is a better solution to the "acceptable AZs for WorkSpaces" problem.)

[YakDriver]

@bflad I try to avoid lint ignoring big blocks of config since offending stuff can be inserted anywhere in the config. But, not sure what else to do here. It's "fixed."

Fixed

[bflad]

Looks good to me, (although the test on this branch is failing for unrelated reasons fixed on the main branch).

Output from acceptance testing in AWS Commercial:

=== CONT  TestAccAwsWorkspacesDirectory_basic
    resource_aws_workspaces_directory_test.go:63: Step 1/2 error: Check failed: 1 error occurred:
        	* Check 16/24 error: aws_workspaces_directory.main: Attribute 'tags.%' expected "0", got "1"

Output from acceptance testing in AWS GovCloud (US):

--- SKIP: TestAccAwsWorkspacesDirectory_basic (2.26s)

[ghost]

This has been released in version 3.24.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 for triage. Thanks!

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!